`Error setting configured user: debian-tor not found` with Sandbox, running as relay
When Sandbox 1
is set, tor is unable to start as a relay running under the debian-tor user. This may be related to #11609 (moved); I don't remember testing the patch with ORPort set. tor is started from init.d script as provided in torproject.org repo, but the binary is compiled from source.
/var/log/tor/log:
May 13 20:30:22.000 [notice] Tor 0.2.5.4-alpha-dev (git-585582fc8c77a199) opening log file.
May 13 20:30:22.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
May 13 20:30:22.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
May 13 20:30:22.000 [notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now.
May 13 20:30:23.000 [warn] Error setting configured user: debian-tor not found
May 13 20:30:23.000 [err] do_main_loop(): Bug: Error initializing keys; exiting
configure:
./configure --disable-asciidoc --prefix=/usr --localstatedir=/var --sysconfdir=/etc --with-tor-user=debian-tor --with-tor-group=debian-tor
/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
torrc:
ORPort 9001
ExitPolicy reject *:*
Sandbox 1
Disabling Sandbox or ORPort will allow Tor to start normally. Problem also exists in b54669bc007adcbe826ec6a531c1719979c06f0b with patch from #11609 (moved) applied, so it doesn't appear to be a regression from the 0.2.5.4-alpha release.
Trac:
Username: alphawolf