Package: tor Version: 0.2.9.9-1 Severity: normal Dear Maintainer,
If I run 'tor' as normal user I can connect to Tor network, i.e. the output of running the command is: ------------------------------------------------------ user@host:~/Downloads/tor-browser_en-US$ tor Feb 17 08:12:15.018 [notice] Tor 0.2.9.9 (git-1d8323c042800718) running on Linux with Libevent 2.0.21-stable, OpenSSL 1.1.0d and Zlib 1.2.8. Feb 17 08:12:15.018 [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 17 08:12:15.018 [notice] Read configuration file "/etc/tor/torrc". Feb 17 08:12:15.021 [notice] Opening Socks listener on 127.0.0.1:9050 Feb 17 08:12:15.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip. Feb 17 08:12:15.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6. Feb 17 08:12:15.000 [notice] Bootstrapped 0%: Starting Feb 17 08:12:15.000 [notice] Bootstrapped 80%: Connecting to the Tor network Feb 17 08:12:16.000 [notice] Bootstrapped 85%: Finishing handshake with first hop Feb 17 08:12:19.000 [notice] Bootstrapped 90%: Establishing a Tor circuit Feb 17 08:12:19.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. Feb 17 08:12:19.000 [notice] Bootstrapped 100%: Done ------------------------------------------------------ But if instead try to use tor daemon, and so after running "sudo systemctl restart tor" I get: ------------------------------------------------------ $ sudo tail -f /var/log/tor/log Feb 17 08:04:27.288 [notice] Read configuration file "/etc/tor/torrc". Feb 17 08:04:27.291 [notice] Opening Socks listener on 127.0.0.1:9050 Feb 17 08:04:27.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip. Feb 17 08:04:27.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6. Feb 17 08:04:27.000 [notice] Bootstrapped 0%: Starting Feb 17 08:04:27.000 [notice] Bootstrapped 80%: Connecting to the Tor network Feb 17 08:04:27.000 [notice] Signaled readiness to systemd Feb 17 08:04:28.000 [notice] Opening Socks listener on /var/run/tor/socks Feb 17 08:04:28.000 [notice] Opening Control listener on /var/run/tor/control Feb 17 08:04:28.000 [notice] Bootstrapped 85%: Finishing handshake with first hop Feb 17 08:06:41.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:2000. Giving up. (waiting for rendezvous desc) Feb 17 08:06:42.000 [notice] No circuits are opened. Relaxed timeout for circuit 1 (a General-purpose client 1-hop circuit in state doing handshakes with channel state open) to 133150ms. However, it appears the circuit has timed out anyway. 2 guards are live. ------------------------------------------------------ And so it doesn't work. I have had recently problems with my university censoring Tor connections (e.g. Tor browser needs to have bridges otherwise it doesn't work), but I don't get why tor run as a normal user works but not as a daemon. This might not be a bug, but I will let you decide. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.8.0-2-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.115 ii init-system-helpers 1.47 ii libc6 2.24-9 ii libevent-2.0-5 2.0.21-stable-2.1 ii libseccomp2 2.3.1-2.1 ii libssl1.1 1.1.0d-2 ii libsystemd0 232-15 ii lsb-base 9.20161125 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages tor recommends: ii logrotate 3.11.0-0.1 ii tor-geoipdb 0.2.9.9-1 ii torsocks 2.2.0-1 Versions of packages tor suggests: pn apparmor-utils <none> pn mixmaster <none> pn obfs4proxy <none> pn obfsproxy <none> ii socat 1.7.3.1-2 pn tor-arm <none> pn torbrowser-launcher <none> -- Configuration Files: /etc/tor/torrc changed [not included] -- no debconf information
