[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: Tor 0.1.0.1-rc is out
- To: or-talk@xxxxxxxxxxxxx
- Subject: Re: Tor 0.1.0.1-rc is out
- From: Roger Dingledine <arma@xxxxxxx>
- Date: Mon, 4 Apr 2005 16:42:00 -0400
- Delivered-to: email@example.com
- Delivered-to: firstname.lastname@example.org
- Delivered-to: email@example.com
- Delivery-date: Mon, 04 Apr 2005 16:42:24 -0400
- In-reply-to: <20050330083230.GA26345@fscked.org>; from firstname.lastname@example.org on Wed, Mar 30, 2005 at 02:32:30AM -0600
- References: <20050328215213.T12832@moria.mit.edu> <20050330083230.GA26345@fscked.org>
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
- User-agent: Mutt/220.127.116.11i
On Wed, Mar 30, 2005 at 02:32:30AM -0600, Mike Perry wrote:
> Awesome. Hidden services are a *LOT* quicker. At least for web.
> Though, as an aside, what is the potential weakness for them that was
> mentioned offhand in your latest draft paper? Is this
> exacerbated/lessened/unchanged by the changes?
Well, there are a number of problems. One of the biggest is that if the
adversary owns a few Tor servers, then over time as the hidden service
makes rendezvous circuits, the adversary's server is likely to end up
as the first hop on the path. What makes it especially bad is that the
adversary can *induce* rendezvous circuits by accessing the hidden service
as normal. If the hidden service is not a Tor server, then it's quickly
clear from timing that the guy who just launched the circuit is probably
the operator of the hidden service. And if he is a Tor server, then basic
predecessor attacks (http://freehaven.net/anonbib/author.html#wright02,
http://freehaven.net/anonbib/author.html#wright03) probably work well.
> Also, got a few other random questions:
> > - Better handling for heterogeneous / unreliable nodes:
> > - Annotate circuits w/ whether they aim to contain high uptime nodes
> > and/or high capacity nodes. When building circuits, choose
> > appropriate nodes.
> Are there any plans to use the ReadHistory/WriteHistory fields in the
> directory servers to also guide circuit creation? Like choosing nodes
> whose bandwidth history is less than their average?
I'm wary of doing this, because I fear oscillation. By the time clients
get ahold of server descriptors, many dozens of minutes have typically
passed. So anything that relies on being quicker than other people about
taking advantage of inefficiencies is not going to work so well.
> Do directory servers otherwise refuse to accept servers that just come
> online and immediately report high uptime? Otherwise there could be a
> possible attack to try to get more people to use a node.
No, we don't try to do any sanity checking yet. The first step is to get
things robust enough in the presence of friendly nodes. Lying nodes is
> > - Make hidden services try to establish a rendezvous for 30 seconds,
> > rather than for n (where n=3) attempts to build a circuit.
> Is this option tunable? Does it have any effect on hidden service
It's not tunable. Should it be?
I picked 30 seconds because that's the default timeout for clients. So
trying longer than that probably won't help because the client will have
given up on this particular rendezvous.
The timeout probably does have some effect on security, but probably not
a big one, compared e.g. to the attack I describe above.