replace directory server with DHT for now.
Andrew Lewman

Andrew Lewman commited on 2010-01-26 16:12:31
Zeige 1 geänderte Dateien mit 5 Einfügungen und 6 Löschungen.

... ...
@@ -41,9 +41,7 @@ hidden server's location (IP address).
41 41
 Step two: the hidden service assembles a <em>hidden service
42 42
 descriptor</em>, containing its public key and a summary of each
43 43
 introduction point, and signs this descriptor with its private key.
44
-It uploads that descriptor to a set of directory servers, again using a
45
-full Tor circuit to hide the link between the directory server storing
46
-the descriptor and the hidden server's IP address. The descriptor will be
44
+It uploads that descriptor to a distributed hash table. The descriptor will be
47 45
 found by clients requesting XYZ.onion where XYZ is a 16 character
48 46
 name that can be uniquely derived from the service's public key. After
49 47
 this step, the hidden service is set up.
... ...
@@ -52,7 +50,7 @@ this step, the hidden service is set up.
52 50
 <p>
53 51
 Although it might seem impractical to use an automatically-generated
54 52
 service name, it serves an important goal: Everyone &ndash; including
55
-the introduction points, the directory servers, and of course the
53
+the introduction points, the distributed hash table directory, and of course the
56 54
 clients &ndash; can verify that they are talking to the right hidden
57 55
 service. See also <a href="https://zooko.com/distnames.html">Zooko's
58 56
 conjecture</a> that out of Decentralized, Secure, and Human-Meaningful,
... ...
@@ -62,7 +60,7 @@ design for hidden service names?
62 60
 </p>
63 61
 
64 62
 <img alt="Tor hidden service step two" src="$(IMGROOT)/THS-2.png" />
65
-# maybe replace "database" with "directory servers"; further: how incorrect
63
+# maybe replace "database" with "DHT"; further: how incorrect
66 64
 # is it to *not* add DB to the Tor cloud, now that begin dir cells are in
67 65
 # use?
68 66
 
... ...
@@ -70,7 +68,8 @@ design for hidden service names?
70 68
 Step three: A client that wants to contact a hidden service needs to
71 69
 learn about its
72 70
 onion address first. After that, the client can initiate connection
73
-establishment by downloading the descriptor from the directory servers. If
71
+establishment by downloading the descriptor from the distributed hash
72
+table. If
74 73
 there is a descriptor for XYZ.onion (the hidden service could also be
75 74
 offline or have left long ago, or there could be a typo in the onion
76 75
 address), the client now knows the set of introduction points and the
77 76