summaryrefslogtreecommitdiff
path: root/docs/DHT_hardening.txt
blob: 1f63c90c7e6aee3fa7ed3d526d817b0f59d9c36d (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
List of possible attacks on the current DHT:

create thousands of fake nodes cloning one client_id and flood our DHT with 
them.

create thousands of "real" nodes that do nothing but shit up our DHT with fake 
crap.

...

Possible solutions:

Each client_id is the public key of the peer so it would be trivial to encrypt 
the DHT requests with crypto_box(). This would completely defeat the first 
attack.

...