diff options
author | irungentoo <irungentoo@gmail.com> | 2013-07-09 18:27:56 -0400 |
---|---|---|
committer | irungentoo <irungentoo@gmail.com> | 2013-07-09 18:27:56 -0400 |
commit | ae6f898a9ef0c046ada8558b7142be2643f9b4c0 (patch) | |
tree | 706ddef64c9ded936ba48754bf0ae2a0772c3096 | |
parent | 803fbafc507a8a19ef83420a462632892413b7f9 (diff) |
Added some thoughts on how to harden the DHT.
-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 new file mode 100644 index 00000000..1f63c90c --- /dev/null +++ b/docs/DHT_hardening.txt | |||
@@ -0,0 +1,17 @@ | |||
1 | List of possible attacks on the current DHT: | ||
2 | |||
3 | create thousands of fake nodes cloning one client_id and flood our DHT with | ||
4 | them. | ||
5 | |||
6 | create thousands of "real" nodes that do nothing but shit up our DHT with fake | ||
7 | crap. | ||
8 | |||
9 | ... | ||
10 | |||
11 | Possible solutions: | ||
12 | |||
13 | 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 | ||
15 | attack. | ||
16 | |||
17 | ... | ||