I'd like some help getting obfs3 set up. I'm seeing an error when I attempt to start an obfsproxy bridge:
Aug 13 06:49:17.000 [notice] Tor 0.2.4.15-rc (git-f41c20b344fb7359) opening new log file. Aug 13 06:49:17.000 [notice] Configured hibernation. This interval began at 2013-08-13 00:00:00; the scheduled wake-up time was 2013-08-13 00:00:00; we expect to exhaust our quota for this interval around 2013-08-14 00:00:00; the next interval begins at 2013-08-14 00:00:00 (all times local) Aug 13 06:49:18.000 [warn] Server managed proxy encountered a method error. (obfs3 could not setup protocol) Aug 13 06:49:18.000 [warn] Managed proxy at '/usr/bin/obfsproxy' failed the configuration protocol and will be destroyed. ... Here's the config: # A unique handle for your server. #Nickname ec2$CONFIG$RESERVATION Nickname gcedemo ContactInfo Lee Colleton <l...@colleton.net> # Set "SocksPort 0" if you plan to run Tor only as a server, and not # make any local application connections yourself. SocksPort 0 # What port to advertise for Tor connections. ORPort 443 # Listen on a port other than the one advertised in ORPort (that is, # advertise 443 but bind to 9001). ORListenAddress 0.0.0.0:9001 # Start Tor as a bridge. BridgeRelay 1 # Run obfsproxy ServerTransportPlugin obfs2,obfs3 exec /usr/bin/obfsproxy --managed ServerTransportListenAddr obfs2 0.0.0.0:52176 ServerTransportListenAddr obfs3 0.0.0.0:40872 # Never send or receive more than 10GB of data per week. The accounting # period runs from 10 AM on the 1st day of the week (Monday) to the same # day and time of the next week. AccountingStart day 0:00 AccountingMax 1 GB BandwidthRate 1MB BandwidthBurst 1GB # Running a bridge relay just passes data to and from the Tor network -- # so it shouldn't expose the operator to abuse complaints. ExitPolicy reject *:* Cheers, Lee -- tor-talk mailing list - tor-talk@lists.torproject.org To unsusbscribe or change other settings go to https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk