From ae6f898a9ef0c046ada8558b7142be2643f9b4c0 Mon Sep 17 00:00:00 2001
From: irungentoo <irungentoo@gmail.com>
Date: Tue, 9 Jul 2013 18:27:56 -0400
Subject: [PATCH] Added some thoughts on how to harden the DHT.

---
 docs/DHT_hardening.txt | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
 create mode 100644 docs/DHT_hardening.txt

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 @@
+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.
+
+...