[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[or-cvs] r14229: Get hidden services explanation page started. (in website/trunk: en images img)

To: or-cvs@xxxxxxxxxxxxx
Subject: [or-cvs] r14229: Get hidden services explanation page started. (in website/trunk: en images img)
From: kloesing@xxxxxxxx
Date: Fri, 28 Mar 2008 19:42:46 -0400 (EDT)
Delivered-to: archiver@xxxxxxxx
Delivered-to: or-cvs-outgoing@xxxxxxxx
Delivered-to: or-cvs@xxxxxxxx
Delivery-date: Fri, 28 Mar 2008 19:42:49 -0400
Reply-to: or-dev@xxxxxxxxxxxxx
Sender: owner-or-cvs@xxxxxxxxxxxxx

Author: kloesing
Date: 2008-03-28 19:42:46 -0400 (Fri, 28 Mar 2008)
New Revision: 14229

Added:
   website/trunk/images/THS-1.png
   website/trunk/images/THS-2.png
   website/trunk/images/THS-3.png
   website/trunk/images/THS-4.png
   website/trunk/images/THS-5.png
   website/trunk/images/THS-6.png
Removed:
   website/trunk/img/THS-1.png
   website/trunk/img/THS-2.png
   website/trunk/img/THS-3.png
   website/trunk/img/THS-4.png
   website/trunk/img/THS-5.png
   website/trunk/img/THS-6.png
Modified:
   website/trunk/en/overview.wml
Log:
Get hidden services explanation page started.

Modified: website/trunk/en/overview.wml
===================================================================
--- website/trunk/en/overview.wml	2008-03-28 05:28:28 UTC (rev 14228)
+++ website/trunk/en/overview.wml	2008-03-28 23:42:46 UTC (rev 14229)
@@ -175,6 +175,87 @@
 the site, and nobody who offered the site would know who was posting to it.
 </p>
 
+<!-- TO TRANSLATORS: this section might still need some review and
+corrections! better wait at least one week from today (2008-03-29) before
+starting translation -->
+
+<p>
+A hidden service needs to advertise its existence in the Tor network before
+clients will be able to contact it. Therefore, the service randomly picks
+some relays, builds circuits to them, and asks them to act as introduction
+points telling them its public key. Note that in the following figures the
+green links are circuits rather than direct connections. This makes it
+impossible for anyone to associate the introduction points with the hidden
+service's IP address. This is important, because although the introduction
+points and others are told the hidden service's identity (public key), they
+must not learn about the hidden server's identity (IP address).
+</p>
+
+<img alt="Tor hidden service step one" src="$(IMGROOT)/THS-1.png" />
+<!-- maybe add a speech bubble containing "PK" to Bob, because that's what
+Bob tells to his introduction points -->
+
+<p>
+In a second step, the hidden service assembles a hidden service descriptor
+containing the introduction points' addresses and its public key and signs
+it with its private key. It stores that descriptor on a set of directory
+servers, again using a circuit that hides the link between storing the
+descriptor with the hidden service's IP address. The descriptor will be
+found by clients requesting XYZ.onion where XYZ is uniquely derived from
+the service's public key. After this step, the hidden service is set up.
+</p>
+
+<img alt="Tor hidden service step two" src="$(IMGROOT)/THS-2.png" />
+<!-- maybe replace "database" with "directory servers"; further: how
+incorrect is it to *not* add DB to the Tor cloud, now that begin dir cells
+are in use? -->
+
+<p>
+A client that wants to contact a hidden service needs to learn about its
+onion address first. After that, the client can initiate connection
+establishment by downloading the descriptor from the directory servers. If
+there is a descriptor for XYZ.onion (the hidden service could also be
+offline or have left long ago, or there could be a typo in the onion
+address), the client creates a circuit to another randomly picked relay and
+asks it to act as rendezvous point, telling it a one-time secret.
+</p>
+
+<img alt="Tor hidden service step three" src="$(IMGROOT)/THS-3.png" />
+<!-- maybe add "cookie" to speech bubble, separated from the surrounded
+"IP1-3" and "PK" -->
+
+<p>
+Upon setting up the rendezvous point, the client assembles an introduce
+message (encrypted to the hidden service's public key) including the
+address of the rendezvous point and the one-time secret. The client sends
+this message to one of the introduction points, requesting it to deliver it
+to the hidden service. Again, communication takes place via a circuit, so
+that nobody can relate sending the introduce message to the client's IP
+address, ensuring the client's anonymity.
+</p>
+
+<img alt="Tor hidden service step four" src="$(IMGROOT)/THS-4.png" />
+
+<p>
+The hidden service decrypts the client's introduce message and finds the
+address of the rendezvous point and the one-time secret in it. The service
+creates a circuit to the rendezvous point and sends the one-time secret to
+it in a rendezvous message.
+</p>
+
+<img alt="Tor hidden service step five" src="$(IMGROOT)/THS-5.png" />
+<!-- it should say "Bob connects to Alice's ..." -->
+
+<p>
+In the last step, the rendezvous point notifies the client about successful
+connection establishment. After that, both, client and hidden service can
+use their circuits to the rendezvous point for communicating with each
+other. The rendezvous point simply relays (end-to-end encrypted) messages
+from client to service and vice versa.
+</p>
+
+<img alt="Tor hidden service step six" src="$(IMGROOT)/THS-6.png" />
+
 <h3>Staying anonymous</h3>
 
 <p>

Copied: website/trunk/images/THS-1.png (from rev 13967, website/trunk/img/THS-1.png)
===================================================================
(Binary files differ)

Copied: website/trunk/images/THS-2.png (from rev 13967, website/trunk/img/THS-2.png)
===================================================================
(Binary files differ)

Copied: website/trunk/images/THS-3.png (from rev 13967, website/trunk/img/THS-3.png)
===================================================================
(Binary files differ)

Copied: website/trunk/images/THS-4.png (from rev 13967, website/trunk/img/THS-4.png)
===================================================================
(Binary files differ)

Copied: website/trunk/images/THS-5.png (from rev 13967, website/trunk/img/THS-5.png)
===================================================================
(Binary files differ)

Copied: website/trunk/images/THS-6.png (from rev 13967, website/trunk/img/THS-6.png)
===================================================================
(Binary files differ)

Deleted: website/trunk/img/THS-1.png
===================================================================
(Binary files differ)

Deleted: website/trunk/img/THS-2.png
===================================================================
(Binary files differ)

Deleted: website/trunk/img/THS-3.png
===================================================================
(Binary files differ)

Deleted: website/trunk/img/THS-4.png
===================================================================
(Binary files differ)

Deleted: website/trunk/img/THS-5.png
===================================================================
(Binary files differ)

Deleted: website/trunk/img/THS-6.png
===================================================================
(Binary files differ)

Prev by Author: [or-cvs] r14052: Working on ticket 75 (in torstatus/trunk: . web)
Next by Author: [or-cvs] r14253: Move hidden service protocol explanations to own page. (website/trunk/en)
Previous by thread: [or-cvs] r14228: we want to pay more people to work on tor. we should tell th (website/trunk/en)
Next by thread: [or-cvs] r14230: Code (disabled) to get way too much info about the contents (in tor/trunk: . src/or)
Index(es):
- Author
- Thread