diff options
-rw-r--r-- | docs/DHT_hardening.txt | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/docs/DHT_hardening.txt b/docs/DHT_hardening.txt index 1f63c90c..59c6ae39 100644 --- a/docs/DHT_hardening.txt +++ b/docs/DHT_hardening.txt | |||
@@ -14,4 +14,21 @@ Each client_id is the public key of the peer so it would be trivial to encrypt | |||
14 | the DHT requests with crypto_box(). This would completely defeat the first | 14 | the DHT requests with crypto_box(). This would completely defeat the first |
15 | attack. | 15 | attack. |
16 | 16 | ||
17 | Make each peer send the information of at least one of his online friends in | ||
18 | every send nodes response. (Might be bad as any node can now know who our | ||
19 | friends are) | ||
20 | |||
21 | Limit the maximum number of peers with identical ips that we keep connected to | ||
22 | in our DHT. (Not a real solution) | ||
23 | |||
24 | Require each node to solve some kind of captcha in order to connect to the | ||
25 | network. (Bad idea.) | ||
26 | |||
27 | Require nodes to crack hashes or solve other computationally intensive | ||
28 | problems in order to be accepted in the network. (Kind of like bitcoin)(This is | ||
29 | probably a bad idea as our application needs to work on phones which are low | ||
30 | power devices) | ||
31 | |||
32 | Make each node test other nodes to see if they respond correctly before sending | ||
33 | them as part of their send nodes response. | ||
17 | ... | 34 | ... |