AdguardTeam / AdguardTeam/AdGuardHome

Split history / split identity

Abierto
#1,283 0 comentarios 0 reacciones 0 asignados Ver en GitHub
enhancement feature request P3: Medium
Lenguaje dominante
TypeScript
Estrellas
36.9k
Forks
2.5k
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

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`.

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.