From: Karsten Loesing <karsten.loesing@gmx.net>
Date: Sun, 4 Jan 2009 00:21:28 +0000 (+0000)
Subject: List places where the hidden service protocol uses SHA-1.
X-Git-Tag: tor-0.2.1.10-alpha~28
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=b4d7776de8b74c68797c6d53ed80a7f682aabcea;p=thirdparty%2Ftor.git

List places where the hidden service protocol uses SHA-1.

svn:r17866
---

diff --git a/doc/spec/proposals/ideas/xxx-what-uses-sha1.txt b/doc/spec/proposals/ideas/xxx-what-uses-sha1.txt
index 00ea56bc3a..9b6e20c586 100644
--- a/doc/spec/proposals/ideas/xxx-what-uses-sha1.txt
+++ b/doc/spec/proposals/ideas/xxx-what-uses-sha1.txt
@@ -102,7 +102,26 @@ What Tor uses hashes for today:
 
 4. The rendezvous protocol
 
-   XXXX write me
+   A. Hidden servers use SHA-1 to establish introduction points on relays,
+      and relays use SHA-1 to check incoming introduction point
+      establishment requests.
+   B. Hidden servers use SHA-1 in multiple places when generating hidden
+      service descriptors.
+   C. Hidden servers performing basic-type client authorization for their
+      services use SHA-1 when encrypting introduction points contained in
+      hidden service descriptors.
+   D. Hidden service directories use SHA-1 to check whether a given hidden
+      service descriptor may be published under a given descriptor
+      identifier or not.
+   E. Hidden servers use SHA-1 to derive .onion addresses of their
+      services.
+   F. Clients use SHA-1 to generate the current hidden service descriptor
+      identifiers for a given .onion address.
+   G. Hidden servers use SHA-1 to remember digests of the first parts of
+      Diffie-Hellman handshakes contained in introduction requests in order
+      to detect replays.
+   H. Hidden servers use SHA-1 during the Diffie-Hellman key exchange with
+      a connecting client.
 
 5. The bridge protocol