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

Re: Another MapAddress option

To: or-talk@xxxxxxxxxxxxx
Subject: Re: Another MapAddress option
From: Nick Mathewson <nickm@xxxxxxxxxxxxx>
Date: Sat, 22 Mar 2008 11:04:17 -0400
Delivered-to: archiver@xxxxxxxx
Delivered-to: or-talk-outgoing@xxxxxxxx
Delivered-to: or-talk@xxxxxxxx
Delivery-date: Sat, 22 Mar 2008 11:04:21 -0400
In-reply-to: <N1B-P_bChtle7j@xxxxxxxxxxxxx>
Mail-followup-to: Nick Mathewson <nickm@xxxxxxxxxxxxx>, or-talk@xxxxxxxxxxxxx
References: <N1B-P_bChtle7j@xxxxxxxxxxxxx>
Reply-to: or-talk@xxxxxxxxxxxxx
Sender: owner-or-talk@xxxxxxxxxxxxx
User-agent: Mutt/1.5.13 (2006-08-11)

On Thu, Mar 20, 2008 at 05:18:51PM -0400, lg2005@xxxxxxxxxxxxx wrote:

> I noticed that when I use MapAddress for one domain in the TOR
> config, all requests that are done in the same time to other domains
> also use the special circuit with "exitnode" at the end.

>  Is it normal? Is there a way so that the special circuit will be
> used ONLY to connect to the site specified in MapAddress?

When Tor needs to build a new path for a stream, it checks whether it
already has a circuit open that will work for that stream.  If there
is already a clean open circuit that could be used, Tor uses that.

It might be neat to add some way to indicate that some addresses or
domains shouldn't share circuits with others.  If anybody wants to
work on this (maybe as part of a gsoc project), that would be pretty neat.

yrs,
-- 
Nick

References:
- Another MapAddress option
  - From: lg2005

Prev by Author: Re: About the MapAddress option
Next by Author: Re: Proposal: Incorporate Unreachable ORs into the Tor Network
Previous by thread: Another MapAddress option
Next by thread: GSoC Idea: Packaging Tor+Vidalia
Index(es):
- Author
- Thread