-
Notifications
You must be signed in to change notification settings - Fork 9
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
Comments
Yep, that's by design! Single hop Tor.
I'm not sure I follow. @mcmanus can you please elaborate? |
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. |
yes to tommy's summary.
…On Thu, Aug 29, 2019 at 7:42 PM Tommy Pauly ***@***.***> wrote:
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.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#35?email_source=notifications&email_token=AAB7TMYOPL7AGHFVMVXYUKTQHBNETA5CNFSM4ISGT4ZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5QDXEY#issuecomment-526400403>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAB7TM4YW3SVNTHABGHEQMTQHBNETANCNFSM4ISGT4ZA>
.
|
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.
The text was updated successfully, but these errors were encountered: