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

Split history / split identity #1283

Open
Revertron opened this issue Dec 20, 2019 · 0 comments
Open

Split history / split identity #1283

Revertron opened this issue Dec 20, 2019 · 0 comments

Comments

@Revertron
Copy link

Imagine you've set 2-3 different upstream DNS-servers, and you resolve some domains by one of them, others by the second and the rest by the third.

If some of them (or all of them) are spying and collecting your browsing history, creating your behavioral identity, they won't get your true history and identity. Only a part of it.

But how to decide which domain to resolve by which upstream?
I propose hashing domains, getting first byte mod number of upstreams.
And for some randomization for different clients - adding some salt for hash.

Then the formula of chosen upstream index becomes:
index = hash(salt + domain)[0] mod upstreams.length

  1. The salt variable can be a simple integer, it doesn't need to be big.
  2. Salt can change after some period of inactivity. It will imitate of client change. Like dynamic IP address.

Hash function does need to be cryptographically strong. It can be even some CRC32 or similar function. And if we use simple integer function like CRC32 we can mod it without getting first byte. Like this: index = crc32(salt + domain) mod upstreams.length.

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