and dirservers are better for non-clique situations

svn:r668
This commit is contained in:
Roger Dingledine 2003-10-24 04:09:10 +00:00
parent b29e29f64a
commit d59864859c

View File

@ -679,11 +679,14 @@ the shared directory is straightforward, and is described in the Tor
specification \cite{tor-spec}. specification \cite{tor-spec}.
% we should, uh, add this to the spec. oh, and write it. -RD % we should, uh, add this to the spec. oh, and write it. -RD
Because the directories are signed, they can be cached at all the other Using directory servers rather than flooding approaches provides
onion routers (or even elsewhere). Thus directory servers are not a simplicity and flexibility. For example, they don't complicate
performance bottleneck when we have many users, and also they won't the analysis when we start experimenting with non-clique network
aid traffic analysis by forcing clients to periodically announce their topologies. And because the directories are signed, they can be cached at
existence to any central point. all the other onion routers (or even elsewhere). Thus directory servers
are not a performance bottleneck when we have many users, and also they
won't aid traffic analysis by forcing clients to periodically announce
their existence to any central point.
\Section{Rendezvous points: location privacy} \Section{Rendezvous points: location privacy}
\label{sec:rendezvous} \label{sec:rendezvous}