Re: [tor-talk] obfsproxy failure: obfs3

2013-08-21 Thread lee colleton
I'm still having trouble connecting to my obfsproxy bridge; Any pointers would be appreciated. External scanning indicates that the correct ports are open except for port 443 but it's definitely open on the firewall. lee@li388-156:~$ nmap -p 22,443,9001,40872,52176 173.255.119.202 Starting Nmap

Re: [tor-talk] obfsproxy failure: obfs3

2013-08-15 Thread lee colleton
When I comment out the ORListenAddress line things look OK. # 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 Aug 15 06:52:50.000 [notice] Tor 0.2.4.16-rc (git-dcf6b6d7dda9ffbd) opening log file. Aug 15

Re: [tor-talk] obfsproxy failure: obfs3

2013-08-15 Thread lee colleton
When I attempt to connect to this bridge, I see a failure in handshaking: Orbot is starting… Orbot is starting… got tor proc id: 27365 Tor process id=27365 Connecting to control port: 9051 SUCCESS connected to control port SUCCESS authenticated to control port Starting Tor client… complete.

Re: [tor-talk] obfsproxy failure: obfs3

2013-08-15 Thread lee colleton
With the ORListenAddress line uncommented, a slightly different failure results: Orbot is starting… Orbot is starting… got tor proc id: 28490 Tor process id=28490 Connecting to control port: 9051 SUCCESS connected to control port SUCCESS authenticated to control port Starting Tor client…

Re: [tor-talk] obfsproxy failure: obfs3

2013-08-15 Thread lee colleton
All of the ports respond on the external IP except for 443 but I can connect via SSL on 9001. I don't understand how ORListenAddress is supposed to work: my bridge times out on 443 but when I comment out the ORListenAddress line it doesn't connect via obfsproxy at all. Please advise. On Thu,

Re: [tor-talk] obfsproxy failure: obfs3

2013-08-15 Thread lee colleton
-tor-relay +tor-relays On Thu, Aug 15, 2013 at 10:13 AM, lee colleton l...@colleton.net wrote: All of the ports respond on the external IP except for 443 but I can connect via SSL on 9001. I don't understand how ORListenAddress is supposed to work: my bridge times out on 443 but when I

Re: [tor-talk] obfsproxy failure: obfs3

2013-08-14 Thread lee colleton
I'm using the development branch with Debian Wheezy per https://www.torproject.org/docs/debian.html.en lee@tor-bootstrap:~$ dpkg -l obfsproxy tor Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required

Re: [tor-talk] obfsproxy failure: obfs3

2013-08-14 Thread George Kadianakis
Hi lee, it seems like you are using an old version of obfsproxy which does not support obfs3. obfsproxy was recently rewritten in Python and that's the version you want to use (the version you are currently using is written in C). That is, you are currently using obfsproxy-0.1.4 but you should be

Re: [tor-talk] obfsproxy failure: obfs3

2013-08-14 Thread lee colleton
My intent is to set up an obfsproxy bridge in the manner of the EC2 images available from cloud.torproject.org which will stay up to date thanks to unattended upgrades. I've enabled wheezy-backports and upgraded thus: lee@tor-bootstrap:~$ dpkg -l tor obfsproxy

Re: [tor-talk] obfsproxy failure: obfs3

2013-08-14 Thread lee colleton
The packaged version of tor complains about support for faster OpenSSL: Aug 14 15:26:52.000 [notice] Tor 0.2.4.16-rc (git-dcf6b6d7dda9ffbd) opening log file. Aug 14 15:26:52.000 [notice] We were built to run on a 64-bit CPU, with OpenSSL 1.0.1 or later, but with a version of OpenSSL that

Re: [tor-talk] obfsproxy failure: obfs3

2013-08-14 Thread Roger Dingledine
On Wed, Aug 14, 2013 at 08:46:32AM -0700, lee colleton wrote: The packaged version of tor complains about support for faster OpenSSL: Aug 14 15:26:52.000 [notice] Tor 0.2.4.16-rc (git-dcf6b6d7dda9ffbd) opening log file. Aug 14 15:26:52.000 [notice] We were built to run on a 64-bit CPU, with

Re: [tor-talk] obfsproxy failure: obfs3

2013-08-14 Thread lee colleton
There's a more serious issue in that my server doesn't appear to be reachable. I've opened tcp:443,9001 along with the two specifiedobfsproxy ports Aug 14 15:26:58.000 [notice] Bootstrapped 100%: Done. Aug 14 15:26:58.000 [notice] Now checking whether ORPort 173.255.119.202:443 is reachable...

Re: [tor-talk] obfsproxy failure: obfs3

2013-08-14 Thread Roger Dingledine
On Wed, Aug 14, 2013 at 09:08:03AM -0700, lee colleton wrote: There's a more serious issue in that my server doesn't appear to be reachable. I've opened tcp:443,9001 along with the two specifiedobfsproxy ports Aug 14 15:26:58.000 [notice] Bootstrapped 100%: Done. Aug 14 15:26:58.000

Re: [tor-talk] obfsproxy failure: obfs3

2013-08-14 Thread lee colleton
Yes, I've opened the ports in the Google Compute Engine (see below). I'll follow up on their forum to make sure I've altered the firewall properly. --lee lee@li388-156:~$ gcutil --service_version=v1beta15 --project=colleton.net:tor-cloud listfirewalls

[tor-talk] obfsproxy failure: obfs3

2013-08-13 Thread lee colleton
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

Re: [tor-talk] obfsproxy failure: obfs3

2013-08-13 Thread Matthew Finkel
On Tue, Aug 13, 2013 at 04:11:18PM -0700, lee colleton wrote: 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]