-
-
Notifications
You must be signed in to change notification settings - Fork 396
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
Usage of constant value for GREASE transport parameter make quinn vulnerable to fingerprinting by quic transport parameters. #2057
Labels
enhancement
New feature or request
Comments
mstyura
added a commit
to mstyura/quinn
that referenced
this issue
Nov 20, 2024
mstyura
added a commit
to mstyura/quinn
that referenced
this issue
Nov 20, 2024
mstyura
added a commit
to mstyura/quinn
that referenced
this issue
Nov 20, 2024
All three of those sound like nice improvements to me! |
mstyura
added a commit
to mstyura/quinn
that referenced
this issue
Nov 20, 2024
mstyura
added a commit
to mstyura/quinn
that referenced
this issue
Nov 20, 2024
mstyura
added a commit
to mstyura/quinn
that referenced
this issue
Nov 21, 2024
mstyura
added a commit
to mstyura/quinn
that referenced
this issue
Nov 21, 2024
mstyura
added a commit
to mstyura/quinn
that referenced
this issue
Nov 21, 2024
mstyura
added a commit
to mstyura/quinn
that referenced
this issue
Nov 21, 2024
mstyura
added a commit
to mstyura/quinn
that referenced
this issue
Nov 22, 2024
mstyura
added a commit
to mstyura/quinn
that referenced
this issue
Nov 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently
quinn
uses constant value asGREASE
reserved random parameter.quinn/quinn-proto/src/transport_parameters.rs
Lines 303 to 305 in 9386cde
This make
quinn
client side users vulnerable to fingerprinting by predictable patterns during handshake. Thanks to ability to inject custom TLS backend like quinn-boring most of TLS handshake is configurable, except the content of quic transport parameters extension.As a prevention actions I see the following steps:
The text was updated successfully, but these errors were encountered: