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.

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

Privacy impact of connection coalescing #645

Closed
mnot opened this issue Nov 16, 2014 · 3 comments
Closed

Privacy impact of connection coalescing #645

mnot opened this issue Nov 16, 2014 · 3 comments

Comments

@mnot
Copy link
Member

mnot commented Nov 16, 2014

Folks in the Tor community point out that coalescing connections is a genuinely new vector for tracking users in HTTP/2.

This should be pointed out in the Privacy Considerations subsection of Security Considerations, along with mitigations.

While we're there, more specific text about mitigating HTTP/2-specific fingerprinting would be nice.

@mnot
Copy link
Member Author

mnot commented Nov 16, 2014

@martinthomson, I've marked this as Design, but I think we can prepare a proposal pretty easily. You want to take a crack at it, or should I do a pull?

@martinthomson
Copy link
Collaborator

I'm happy to take input. Since I'm basically offline this week, getting a start would help lots.

mnot added a commit that referenced this issue Nov 21, 2014
... using connection correlation. This fixes #645.
@mnot mnot mentioned this issue Nov 21, 2014
@mnot
Copy link
Member Author

mnot commented Nov 25, 2014

Marked as editor-ready; please consider list feedback.

@mnot mnot closed this as completed in 9515019 Nov 25, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants