Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #18457

Closed (moved)
Open
Opened Mar 01, 2016 by weasel (Peter Palfrader)@weasel

continues to start on unix socket open errors

On 0.2.8.x, Tor will no longer fail to start when it cannot open a unix SocksPort and user switching is enabled.

weasel@defiant:~$ sudo -H -i /usr/sbin/tor DataDirectory /home/weasel/.tor User weasel SocksPort unix:/home/weasel/test/socks
Mar 01 18:29:11.507 [notice] Tor v0.2.8.1-alpha (git-75e920591fe94bf6) running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.1k and Zlib 1.2.8.
Mar 01 18:29:11.508 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Mar 01 18:29:11.508 [notice] This version is not a stable Tor release. Expect more bugs than usual.
Mar 01 18:29:11.508 [notice] Read configuration file "/etc/tor/torrc".
Mar 01 18:29:11.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Mar 01 18:29:11.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Mar 01 18:29:11.000 [notice] Bootstrapped 0%: Starting
Mar 01 18:29:11.000 [notice] Bootstrapped 80%: Connecting to the Tor network
Mar 01 18:29:12.000 [warn] Permissions on directory /home/weasel/test are too permissive.
Mar 01 18:29:12.000 [warn] Before Tor can create a SOCKS socket in "/home/weasel/test/socks", the directory "/home/weasel/test" needs to exist, and to be accessible only by the user account that is running Tor.  (On some Unix systems, anybody who can list a socket can connect to it, so Tor is being careful.)
Mar 01 18:29:12.000 [notice] Bootstrapped 85%: Finishing handshake with first hop
Mar 01 18:29:13.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
Mar 01 18:29:13.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Mar 01 18:29:13.000 [notice] Bootstrapped 100%: Done
^C

(there is no socket when it's running)

Without user switching:

weasel@defiant:~$ /usr/sbin/tor DataDirectory /home/weasel/.tor User weasel SocksPort unix:/home/weasel/test/socks     
Mar 01 18:30:38.444 [notice] Tor v0.2.8.1-alpha (git-75e920591fe94bf6) running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.1k and Zlib 1.2.8.
Mar 01 18:30:38.444 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Mar 01 18:30:38.444 [notice] This version is not a stable Tor release. Expect more bugs than usual.
Mar 01 18:30:38.444 [notice] Read configuration file "/etc/tor/torrc".
Mar 01 18:30:38.449 [warn] Permissions on directory /home/weasel/test are too permissive.
Mar 01 18:30:38.449 [warn] Before Tor can create a SOCKS socket in "/home/weasel/test/socks", the directory "/home/weasel/test" needs to exist, and to be accessible only by the user account that is running Tor.  (On some Unix systems, anybody who can list a socket can connect to it, so Tor is being careful.)
Mar 01 18:30:38.449 [warn] Failed to parse/validate config: Failed to bind one of the listener ports.
Mar 01 18:30:38.449 [err] Reading config failed--see warnings above.

For comparison, 0.2.7.x:

drwxr-xr-x 2 weasel weasel 4096 Mar  1 18:17 test/
weasel@defiant:~$ sudo -H -i /usr/sbin/tor DataDirectory /home/weasel/.tor User weasel SocksPort unix:/home/weasel/test/socks
Mar 01 18:27:21.782 [notice] Tor v0.2.7.6 (git-605ae665009853bd) running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.1k and Zlib 1.2.8.
Mar 01 18:27:21.782 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Mar 01 18:27:21.782 [notice] Read configuration file "/etc/tor/torrc".
Mar 01 18:27:21.787 [warn] Permissions on directory /home/weasel/test are too permissive.
Mar 01 18:27:21.787 [warn] Before Tor can create a SOCKS socket in "/home/weasel/test/socks", the directory "/home/weasel/test" needs to exist, and to be accessible only by the user account that is running Tor.  (On some Unix systems, anybody who can list a socket can connect to it, so Tor is being careful.)
Mar 01 18:27:21.787 [warn] Failed to parse/validate config: Failed to bind one of the listener ports.
Mar 01 18:27:21.787 [err] Reading config failed--see warnings above.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#18457