[tor-bugs] #15261 [Tor]: torrc's SocksSocket breaks tor-service-defaults-torrc's SocksPort

[Tor Bug Tracker & Wiki]

#15261: torrc's SocksSocket breaks tor-service-defaults-torrc's SocksPort
--------------------+------------------------------------
 Reporter:  proper  |          Owner:
     Type:  defect  |         Status:  new
 Priority:  normal  |      Milestone:  Tor: 0.2.6.x-final
Component:  Tor     |        Version:  Tor: 0.2.6.4-rc
 Keywords:          |  Actual Points:
Parent ID:          |         Points:
--------------------+------------------------------------
 Related:
 #12585

 -----

 Operating system:
 Debian wheezy

 -----

 Version:
 {{{
 Tor v0.2.6.4-rc (git-b7090ba4fb85d8ac) running on Linux with Libevent
 2.0.19-stable, OpenSSL 1.0.1e and Zlib 1.2.7.
 }}}

 -----

 This is my {{{/usr/share/tor/tor-service-defaults-torrc}}}:

 {{{
 DataDirectory /var/lib/tor
 PidFile /var/run/tor/tor.pid
 RunAsDaemon 1
 User debian-tor

 ControlSocket /var/run/tor/control
 ControlSocketsGroupWritable 1

 CookieAuthentication 1
 CookieAuthFileGroupReadable 1
 CookieAuthFile /var/run/tor/control.authcookie

 Log notice file /var/log/tor/log

 ## (A) not working
 SocksPort 9102
 }}}

 All instances are defaults that come with Debian. Only `SocksPort 9102`
 was added by me.

 -----

 This is my very minimal {{{/etc/tor/torrc}}} to keep this report simple:

 {{{
 ## (B) works
 #SocksPort 9102

 ## (C)
 SocksSocketsGroupWritable 1
 ## (D)
 SocksPort unix:/var/run/tor/socket
 }}}

 -----

 Legend:

 * enabled -> commented in
 * disabled -> commented out

 -----

 Result:

 When (A) `SocksPort 9102` is enabled, and (D) `SocksPort
 unix:/var/run/tor/socket` is disabled, then `127.0.0.1 9102` is reachable.

 When (A) `SocksPort 9102` is enabled, and (B) `SocksPort 9102` is
 disabled, and (D) `SocksPort unix:/var/run/tor/socket` is enabled, then
 `127.0.0.1 9102` is unreachable.

 When (A) and (B) `SocksPort 9102` is enabled, and (D) `SocksPort
 unix:/var/run/tor/socket` is enabled, then `127.0.0.1 9102` is reachable.

 -----

 Expected result:

 If `SocksPort 9102` is set in {{{/usr/share/tor/tor-service-defaults-
 torrc}}} and `SocksPort unix:/var/run/tor/socket` is set in
 `/etc/tor/torrc`, then the SocksSocket should not interfere with
 `SocksPort 9102`.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/15261>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online