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

concerns about proxy and target selection #35

Open
mcmanus opened this issue Aug 29, 2019 · 3 comments
Open

concerns about proxy and target selection #35

mcmanus opened this issue Aug 29, 2019 · 3 comments

Comments

@mcmanus
Copy link
Collaborator

mcmanus commented Aug 29, 2019

if a proxy and target collude then the client address and DNS information are trivially correlated.

If a single entity has more than one origin in the list of known targets then a client will eventually route a 'blinded' request through both of them creating an unfortunate liability.

it seems useful to have some way of marking this kind of redundancy.

we might also want to encourage doh servers to use anycast and/or geo-dns to minimize origin names and the potential for conflict.

@chris-wood
Copy link
Collaborator

if a proxy and target collude then the client address and DNS information are trivially correlated.

Yep, that's by design! Single hop Tor.

If a single entity has more than one origin in the list of known targets then a client will eventually route a 'blinded' request through both of them creating an unfortunate liability.

I'm not sure I follow. @mcmanus can you please elaborate?

@tfpauly
Copy link
Owner

tfpauly commented Aug 29, 2019

I think the point here is that if I end up selecting two nodes that both belong to Apple, Apple could more easily collude with itself (even accidentally) to correlate information. It is beneficial for the client to be aware of boundaries between servers that are safe to use for proxying.

@mcmanus
Copy link
Collaborator Author

mcmanus commented Aug 30, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants