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

Tracking by replaying a flight of 0-RTT data #1334

Closed
wants to merge 1 commit into from
Closed

Tracking by replaying a flight of 0-RTT data #1334

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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-tls-rfc8446bis.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5337,6 +5337,12 @@ applications SHOULD NOT offer tickets across connections that are meant to be
uncorrelated. For example, {{FETCH}} defines network partition keys to separate
cache lookups in web browsers.

The attack described in {{anti-replay}} where a network attacker mounts an attack by
replaying a flight of 0-RTT data, can also be used to determine that a server,
located in different locations or utilizing different network addresses,
is in fact, one and the same. The mitigations outlined in {{anti-replay}} also prevent
this tracking attack.

Clients and Servers SHOULD NOT reuse a key share for multiple connections. Reuse
of a key share allows passive observers to correlate different connections. Reuse
of a client key share to the same server additionally allows the server to correlate different connections.
Expand Down
Loading