Dear fellows,
maybe you can help out. And maybe I missed some information on my Tor version. I run an obfuscated bridge (Tor 0.2.5.8-rc (git-eaa9ca1011e73a9d)) on Ubuntu 12.04 and wanted to enable the scramblesuit pluggable transport.
When changing my line in torrc to
ServerTransportPlugin obfs3,scramblesuit exec /usr/bin/obfsproxy managed
I get the following warning in the logs:
[warn] The communication stream of managed proxy '/usr/bin/obfsproxy' is 'closed'. Most probably the managed proxy stopped running. This might be a bug of the managed proxy, a bug of Tor, or a misconfiguration. Please enable logging on your managed proxy and check the logs for errors. [notice] Failed to terminate process with PID '18171' ('Success').
Obfs3-only works like a charm without complaints. (ServerTransportPlugin obfs3 exec /usr/bin/obfsproxy managed)
I set my ExtORPort to "auto", pyptlib is installed, packages from obfsproxy and pyptlib are in the right locations and I use the shipped apparmor profile for Tor for Ubuntus.
Even if I stop apparmor service, I don't get better results.
I thought it was a permissions problem somehow as --log-min-severity=debug --log-file=/home/me/obfs.log won't even create the logfile so that obfsproxy fails from the very beginning.
But, as I said, obfs3-only works without problems.
Any ideas? Thank you in advance.
Kind regards
christian
Christian transcribed 1.5K bytes:
I thought it was a permissions problem somehow as --log-min-severity=debug --log-file=/home/me/obfs.log won't even create the logfile so that obfsproxy fails from the very beginning.
Try that again with `--log-min-severity debug --log-file /home/me/obfs.log`.
tor-relays@lists.torproject.org