From 72f5f86f70556fc273475bbe58d90b1da2b944e1 Mon Sep 17 00:00:00 2001 From: Roger Dingledine Date: Wed, 31 Mar 2004 22:58:15 +0000 Subject: [PATCH] specify that alice and bob can use dirty circuits when uploading or fetching hidserv descriptors svn:r1416 --- trunk/doc/rend-spec.txt | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/trunk/doc/rend-spec.txt b/trunk/doc/rend-spec.txt index 5dfbbd75d9..5a1ef49a9e 100644 --- a/trunk/doc/rend-spec.txt +++ b/trunk/doc/rend-spec.txt @@ -150,6 +150,7 @@ Tor Rendezvous Spec 1.4. Bob's OP advertises his server descriptor Bob's OP opens a stream to each directory server's directory port via Tor. + (He may re-use old circuits for this.) Over this stream, Bob's OP makes an HTTP 'POST' request, to the URL '/rendezvous/publish' (relative to the directory server's root), containing as its body Bob's service descriptor. Upon receiving a @@ -188,9 +189,10 @@ Tor Rendezvous Spec Alice opens a stream to a directory server via Tor, and makes an HTTP GET request for the document '/rendezvous/', where ' is replaced with the - encoding of Bob's public key as described above. The directory replies - with a 404 HTTP response if it does not recognize , and otherwise - returns Bob's most recently uploaded service descriptor. + encoding of Bob's public key as described above. (She may re-use old + circuits for this.) The directory replies with a 404 HTTP response if + it does not recognize , and otherwise returns Bob's most recently + uploaded service descriptor. If Alice's OP receives a 404 response, it tries the other directory servers, and only fails the lookup if none recognizes the public key hash.