Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Buffer Short packets if the handshake is not complete #320

Closed
camshaft opened this issue Dec 14, 2020 · 1 comment · Fixed by #2270
Closed

Buffer Short packets if the handshake is not complete #320

camshaft opened this issue Dec 14, 2020 · 1 comment · Fixed by #2270
Assignees
@WesleyRosenblum
Labels
compliance:MAY compliance

Comments

@camshaft
Copy link
Contributor

camshaft commented Dec 14, 2020 •
edited
Loading

From Receiving Out-of-Order Protected Packets in draft-ietf-quic-tls-32:

Received
packets protected with 1-RTT keys MAY be stored and later decrypted
and used once the handshake is complete.

Also in the case of 0-RTT:

A server could receive packets protected with 0-RTT keys prior to
receiving a TLS ClientHello. The server MAY retain these packets for
later decryption in anticipation of receiving a ClientHello.
@WesleyRosenblum
Copy link
Contributor

remove references in

s2n-quic/quic/s2n-quic-transport/src/connection/connection_impl.rs

Line 1480 in ec6f50d

//= tracking-issue=320
and close

@WesleyRosenblum WesleyRosenblum self-assigned this Jul 11, 2024
@WesleyRosenblum WesleyRosenblum mentioned this issue Jul 11, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@WesleyRosenblum WesleyRosenblum

Labels
compliance:MAY compliance
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

docs(s2n-quic): cleaning up references to old issues aws/s2n-quic
2 participants
@camshaft @WesleyRosenblum