4 of 6 standards met
Tested Build v2025.02.10.00 Observation We observed that the server implementation cannot handle two Initial packets within a single datagram. We send a TLS ClientHello split into two CRYPTO frames, each placed into its own Initial packet, and coalesce both packets into one datagram. Upon receiving the datagram, the server does not send any response. This issue appears to be specific to Initial packets: for Handshake packets, we could not observe the same behavior. This is not a security issue, but it deviates from RFC 9000, which allows coalescing multiple Initial packets into a single datagram: https://datatracker.ietf.org/doc/html/rfc9000#section-12.2 Is there any reason why the implementation handles coalesced Initial packets this way?
Repository: facebook/mvfst. Description: An implementation of the QUIC transport protocol. Stars: 1637, Forks: 279. Primary language: C++. Languages: C++ (89.4%), Python (5%), CMake (2.9%), Starlark (2.2%), Shell (0.2%). License: MIT. Open PRs: 5, open issues: 39. Last activity: 6h ago. Community health: 75%. Top contributors: jbeshay, mjoras, kvtsoy, hanidamlaj, ahornby, lnicco, wez, deadalnix, simpkins, afrind and others.
Last 12 weeks · 325 commits
Summary Upgrade GitHub Actions to their latest versions to ensure compatibility with Node 24, as Node 20 will reach end-of-life in April 2026. Changes Context Per GitHub's announcement, Node 20 is being deprecated and runners will begin using Node 24 by default starting March 4th, 2026. Why this matters Node 20 EOL: April 2026 Node 24 default: March 4th, 2026 Action**: Update to latest action versions that support Node 24 Security Note Actions that were previously pinned to commit SHAs remain pinned to SHAs (updated to the latest release SHA) to maintain the security benefits of immutable references. Testing These changes only affect CI/CD workflow configurations and should not impact application functionality. The workflows should be tested by running them on a branch before merging.
fix #419