[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: Selecting and using a particular Tor IP address
- To: or-talk@xxxxxxxxxxxxx
- Subject: Re: Selecting and using a particular Tor IP address
- From: "Michael_google gmail_Gersten" <keybounce@xxxxxxxxx>
- Date: Sat, 28 Apr 2007 07:38:45 -0700
- Delivered-to: email@example.com
- Delivered-to: firstname.lastname@example.org
- Delivered-to: email@example.com
- Delivery-date: Sat, 28 Apr 2007 10:39:12 -0400
- Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=TnzdcpPnbsgttmf+WH9V1S3IGizCLmZn23Y7jaT4rLUJbPqRbY/7JCi3IUI1U/UEi1AE27BN2pR+H+sVGXklZrJGT2+6NjImc8bWcTk7KgUVAe/DmMJkcXH5DgWL45UV94d6YVsFkHQpXZCne/Hl8VEbchbCaPfaVOJ42NuhJ/E=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=dMKX+FGa4OSQEzWrI8SdVh1afqiMchg4QBdKjXySHtc+bEx2qbaMhBQ0yrKgyASJV1LLw/SxPldgsLS8/WD4YrUsE2Ha9MsmdN37DRvfMF18aRIsgepDsAvoUmBDJWBqtyVz/R0taLO88DedTpp/O9MozLw2T0D5kYCJW2TvXvs=
- In-reply-to: <firstname.lastname@example.org>
- References: <email@example.com> <firstname.lastname@example.org>
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
On 4/25/07, F M <cantinabandsong@xxxxxxxxx> wrote:
Thanks for the tip. I'm a bit new to this, so please
forgive the dumb question, but where do you find the
nodename? Is this the IP address?
If you are using the .exit "hostname" to force a specific tor exit
node, then you use that particular tor node name.
A quick, dirty, but mostly working system is to add port 80 to the
long lived port list; this makes high uptime nodes more likely (almost
certainty). Keep in mind that this isn't perfect; if a circuit is
unused for 10 minutes, or more than an hour old, it will be rotated.
My solution? Since this is very common -- all PhPBBS sites, and some
others -- I just add these as exceptions in my privoxy config, so that
they never go through tor. I'm already signing in to the BBS forum, so
they know who I am. Avoiding Tor tells both my ISP and their ISP about
A solution that keeps Tor and these nodes?
Combine both "TrackHostExits" and long lived ports.
That adds port 80 to the default list (Boo! I have to respecify the
whole list just to add one port).
That says to make sure that any connection to that host will use the
same exit node.
Warning #1: If the exit Tor node goes down, Tor won't help you on
this. Hence, you want to use the LongLivedPorts to avoid this. (Yea,
that bit me a lot at first.)
Warning #2: Tor makes a 4 hop circuit, not a 3 hop circuit, for
secondary connections when you use this. I don't know why --
seriously, why first make a normal three hop, and then extend to a
forced exit node, rather than making a short two hop, and then extend
to a forced exit node?