-
-
Notifications
You must be signed in to change notification settings - Fork 385
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.
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
After planned migration, connection is linkable to prev. path #1803
Labels
bug
Something isn't working
Comments
nemethf
added a commit
to nemethf/quinn
that referenced
this issue
Apr 3, 2024
(See bug quinn-rs#1803 for the server-side case.)
Ralith
pushed a commit
to nemethf/quinn
that referenced
this issue
Apr 4, 2024
(See bug quinn-rs#1803 for the server-side case.)
Ralith
pushed a commit
to nemethf/quinn
that referenced
this issue
Apr 4, 2024
(See bug quinn-rs#1803 for the server-side case.)
Ralith
pushed a commit
that referenced
this issue
Apr 4, 2024
(See bug #1803 for the server-side case.)
gabrik
pushed a commit
to gabrik/quinn
that referenced
this issue
Apr 4, 2024
(See bug quinn-rs#1803 for the server-side case.)
#1857 should sort this out. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The server switches to a new CID, but it sends a path-challenge on the old path with the new CID. So it is still possible to trace back the connection to the old path after the client switches to a new socket.
See #1800 for breaking linkability on the client side.
The text was updated successfully, but these errors were encountered: