Thanks. Editing it unbeknownst to Vidalia did the trick :) Since the first two lines of torrc read:
# This file was generated by Tor; if you edit it, comments will not be preserved # The old torrc file was renamed to torrc.orig.1 or similar, and Tor will ignore it
It leaves me confused as to whether the deletion is the fault of Vidalia or Tor. There's actually another more minor glitch in the build of Vidalia I got with editing torrc for a running instance of Tor -- you have to use the "Apply selection only" option when saving your changes, or else delete the comment lines from the top (with the comment lines in place and the "Apply all" option, you get the error message 'Error at line 1: ""'.
I'll look into reporting both those issues when I get the chance.
Hoping my bridge gets put to good use soon :)...
Thanks again, George. Asa ===== P.S. .. breaking news in the US, CISPA just passed; privacy ante for US citizens has just doubled.
-----Original Message----- From: tor-relays-bounces@lists.torproject.org [mailto:tor-relays-bounces@lists.torproject.org] On Behalf Of George Kadianakis Sent: Thursday, April 18, 2013 8:01 AM To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] Trying to set up an obfs2/3 bridge on Windows, missing something.
"Asa Rossoff" asa@lovetour.info writes:
I think I'm suppling the ServerTransport parameters incorrectly. the log seems to indicate it is listening on the wrong ports for obfs2 and obfs3.
Since it was the only compiled package I saw for Windows with obfs
support,
I downloaded the tor-pluggable-transports-browser-2.4.11-alpha-2.
I am using the following .torrc --
Address *obfuscated*
AvoidDiskWrites 1
<snip>
HardwareAccel 1
ServerTransportPlugin obfs2,obfs3 exec pyobfsproxy managed
ServerTransportListenAddr obfs2,obfs3 0.0.0.0:56831 0.0.0.0:56832
Log notice stdout
<snip>
Any help? Is it just a syntax error on my part (I tried using two lines
for
the ServerTransportListenAddr but one was automatically deleted after editing in Vidalia), or am I further off-track?
The correct way to do what you want is: """ ServerTransportListenAddr obfs2 0.0.0.0:56831 ServerTransportListenAddr obfs3 0.0.0.0:56832 """ I just tested it in my bridge and it works.
Although Tor should have warned you that you are doing it wrong. I opened a ticket for this: https://trac.torproject.org/projects/tor/ticket/8727
Unfortunately, I don't know why Vidalia deleted your ServerTransportListenAddr lines when you tried to split them into two lines. I'm not using Vidalia when I run bridges.
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays