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

Add a section on what to do when unprotecting a packet fails #345

Merged
merged 3 commits into from
Mar 10, 2017
Merged

Add a section on what to do when unprotecting a packet fails #345

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ef7f5c3
Add a section on what to do when unprotecting a packet fails (hint: t…
martinthomson Feb 24, 2017
da610a0
Deal with bad key phase changes somehow
martinthomson Mar 2, 2017
081c551
Making it clear that an endpoint using an old key is indeciperable fr…
seanturner Mar 10, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions draft-ietf-quic-tls.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1004,6 +1004,12 @@ confused for retransmissions of handshake messages. A client cannot initiate a
key update until all of its handshake messages have been acknowledged by the
server.

A packet that triggers a key update could arrive after successfully processing a
packet with a higher packet number. This is only possible if there is a key
compromise and an attack, or if the peer is incorrectly reverting to use of old
keys. An endpoint MUST immediately terminate the connection if it detects this
condition.


# Client Address Validation {#client-address-validation}

Expand Down