Package: tor
Version: 0.2.6.1-alpha-1
Severity: normal
(Note: I tried the version of Tor in testing first.)
Here is the config line from my torrc:
ClientTransportPlugin obfs3 exec /usr/bin/obfsproxy --log-min-severity info
--log-file /tmp/obfsproxy.log managed
And here is what I get in /var/log/tor/log on every restart:
"The communication stream of managed proxy '/usr/bin/obfsproxy' is 'closed'.
Most probably the managed proxy
stopped running. <etc....>"
Then I added the logging bits in the ClientTransportPlugin line above. But, no
/tmp/obfsproxy.log
file is created. However, if I run
/usr/bin/obfsproxy --log-min-severity info --log-file
/tmp/obfsproxy.log managed
straight from the command line, a /tmp/obfsproxy.log is created.
>From this I infer that Tor is never getting to the point of starting obfsproxy.
Perhaps there is an issue with the Debian environment?
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (800, 'testing'), (700, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages tor depends on:
ii adduser 3.113+nmu3
ii libc6 2.19-13
ii libevent-2.0-5 2.0.21-stable-1.1
ii libseccomp2 2.1.1-1
ii libssl1.0.0 1.0.1j-1
ii lsb-base 4.1+Debian13+nmu1
ii zlib1g 1:1.2.8.dfsg-2+b1
Versions of packages tor recommends:
ii logrotate 3.8.7-1+b1
ii tor-geoipdb 0.2.5.10-1
ii torsocks 2.0.0-3
Versions of packages tor suggests:
pn apparmor-utils <none>
pn mixmaster <none>
ii obfsproxy 0.2.12-1
ii privoxy 3.0.21-4
pn socat <none>
pn tor-arm <none>
pn xul-ext-torbutton <none>
-- Configuration Files:
/etc/tor/torrc changed [not included]
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
