[tor-talk] Tor + obfsproxy on Centos 6

me ya m3282564 at gmail.com
Fri Feb 10 23:05:43 UTC 2012

Has anyone succeeded in getting this combination to run on a RedHat distro?

Both Tor and obfsproxy compile and run (i think):

[obfs at gryphon obfsproxy]$ obfsproxy obfs2 --dest= server &[1] 3228
[obfs at gryphon obfsproxy]$ cat /etc/torrc SocksPort 0
ORPort 9001BridgeRelay 1
Exitpolicy reject *:*ServerTransportPlugin obfs2 exec
/usr/local/bin/obfsproxy --managed --log-file=/var/log/tor/obfsproxy.log
# Log debug file /var/log/tor/log
[obfs at gryphon obfsproxy]$ tor -f /etc/torrc &[2]
3230[obfs at gryphonobfsproxy]$ Feb 11 01:58:40.142 [notice] Tor
(git-9ce9836f853d8a31) running on Linux i686.
Feb 11 01:58:40.142 [notice] Tor can't help you if you use it wrong! Learn
how to be safe at https://www.torproject.org/download/download#warning
Feb 11 01:58:40.142 [notice] This version is not a stable Tor release.
Expect more bugs than usual.Feb 11 01:58:40.142 [notice] Read configuration
file "/etc/torrc".
Feb 11 01:58:40.143 [notice] Your ContactInfo config option is not set.
Please consider setting it, so we can contact you if your server is
misconfigured or something else goes wrong.
Feb 11 01:58:40.144 [notice] Initialized libevent version 2.0.16-stable
using method epoll (with changelist). Good.
Feb 11 01:58:40.144 [notice] Opening OR listener on 11
01:58:40.000 [notice] Parsing GEOIP file /usr/local/share/tor/geoip.
Feb 11 01:58:40.000 [notice] Configured to measure statistics. Look for the
*-stats files that will first be written to the data directory in 24 hours
from now.
Feb 11 01:58:40.000 [notice] No AES engine found; using AES_* functions.
Feb 11 01:58:40.000 [notice] This OpenSSL has a buggy version of counter
mode; not using it.
Feb 11 01:58:40.000 [notice] OpenSSL OpenSSL 1.0.0-fips 29 Mar 2010 looks
like version 0.9.8m or later; I will try SSL_OP to enable renegotiation
Feb 11 01:58:40.000 [notice] Your Tor server's identity key fingerprint is
'Unnamed CB38FAA398ABD24AD695D26BF8842423B1FB9137'
Feb 11 01:58:40.000 [notice] Reloaded microdescriptor cache.  Found 3409
Feb 11 01:58:41.000 [notice] We now have enough directory information to
build circuits.
Feb 11 01:58:41.000 [notice] Bootstrapped 80%: Connecting to the Tor
Feb 11 01:58:42.000 [notice] Heartbeat: Tor's uptime is 0:00 hours, with 2
circuits open. I've sent 0 kB and received 0 kB.
Feb 11 01:58:42.000 [notice] Bootstrapped 85%: Finishing handshake with
first hop.
Feb 11 01:58:42.000 [notice] Bootstrapped 90%: Establishing a Tor circuit.
Feb 11 01:58:43.000 [notice] Managed proxy stream closed. Most probably
application stopped running
Feb 11 01:58:43.000 [notice] Failed to terminate process with PID '3235'
Feb 11 01:58:43.000 [notice] Tor has successfully opened a circuit. Looks
like client functionality is working.
Feb 11 01:58:43.000 [notice] Bootstrapped 100%: Done.
Feb 11 01:58:43.000 [notice] Now checking whether ORPort xx.xx.xxx.xx:9001
is reachable... (this may take up to 20 minutes -- look for log messages
indicating success)
Feb 11 01:58:43.000 [notice] Self-testing indicates your ORPort is
reachable from the outside. Excellent. Publishing server descriptor.
Feb 11 02:02:06.000 [notice] Performing bandwidth self-test...done.

obfs2 never turns up. Is it crashing at Feb 11 01:58:43.000?


More information about the tor-talk mailing list