mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-11-20 02:09:24 +01:00
and dirservers are better for non-clique situations
svn:r668
This commit is contained in:
parent
b29e29f64a
commit
d59864859c
@ -679,11 +679,14 @@ the shared directory is straightforward, and is described in the Tor
|
||||
specification \cite{tor-spec}.
|
||||
% 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
|
||||
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.
|
||||
Using directory servers rather than flooding approaches provides
|
||||
simplicity and flexibility. For example, they don't complicate
|
||||
the analysis when we start experimenting with non-clique network
|
||||
topologies. And because the directories are signed, they can be cached at
|
||||
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}
|
||||
\label{sec:rendezvous}
|
||||
|
Loading…
Reference in New Issue
Block a user