[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: Tor 0.2.0.9-alpha is out
- To: or-talk@xxxxxxxxxxxxx
- Subject: Re: Tor 0.2.0.9-alpha is out
- From: "John Kimble" <det.j.kimble@xxxxxxxxx>
- Date: Sun, 28 Oct 2007 22:39:08 +0800
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-talk-outgoing@xxxxxxxx
- Delivered-to: or-talk@xxxxxxxx
- Delivery-date: Sun, 28 Oct 2007 10:39:18 -0400
- Dkim-signature: v=1; a=rsa-sha256; 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; bh=AwGgdDzQcjPhWCjPa+5YbQjw9yCmVLE9z3oFcuTukog=; b=H/rFBUW+aPO9LYV4ZuYLRjwWS3BZ0Zb2z094YQam+JbukaHF0Y7H5kIwExRRWuUvGExNOgW4Xq8nly7TSpzdLYkatRn7mHLZTLgxKNHS+X0sMXyw47dISPDiSfjKTVgPVvegqTJMsdcO74iGO00bXR0xrPgPILiBufwifBxAPo4=
- 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=A4I5twTqcML4/3jEXt66qCs+g9cBfi1jlJAs9AwdT0N04CPEtFFx7RAWwy1i5IpUhPy8SFHB9iJaK9FqKLUTdxkr5Ed4s8puQDFfU7ffL6/Rm8lKcd4I82G3ziQKILv6sw+AlKx++SG7CEig1iJZ2pnaggc+2ANSD/dnk+phLjk=
- In-reply-to: <20071026211940.GZ20791@xxxxxxxxxxxxxx>
- References: <20071026211940.GZ20791@xxxxxxxxxxxxxx>
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
It is worth noting that the Vidalia bundle for Tor 0.2.0.9-alpha comes
with Vidalia 0.0.15, which manages its own torrc file, and in some
cases this can cause problems. This is not a bug within Tor itself,
but readers of this mailing list who use the Vidalia bundle should
When you start up Vidalia for the first time, it does use the torrc
you supplied to start Tor, so your settings are used. Then Vidalia
would overwrite torrc with its own version, which for the most part
does preserve whatever custom torrc settings you had (e.g. HttpProxy
and ExcludeNodes), but some other settings are not preserved (e.g.
__allDirActionsPrivate). So next time you start Vidalia, it will be
using its own version of torrc, without some of your custom settings.
For those who depend on __allDirActionsPrivate (e.g. to stay under the
radar of an overzealous WebSense filter), this means every time after
running Vidalia, you'll have to edit torrc and add
"__allDirActionsPrivate 1" back in.
A ticket has already been filed with the Vidalia project regarding this issue.