Opened 6 years ago

Closed 6 years ago

#12115 closed defect (fixed)

Sandbox: Stack trace after HUP when changing DirPort, ORPort, or DisableNetwork

Reported by: alphawolf Owned by:
Priority: Medium Milestone: Tor: 0.2.5.x-final
Component: Core Tor/Tor Version: Tor:
Severity: Keywords: sandbox
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Stack trace generated when sandbox is enabled and DirPort or ORPort is changed, or DisableNetwork is changed from 1 to 0. In each case the stack trace is identical, and all that varies is what type of listener is being opened on the previous log line.

May 23 17:35:26.000 [notice] Opening OR listener on

============================================================ T= 1400880926
(Sandbox) Caught a bad syscall attempt (syscall listen)

Tor built from latest master (git-824bebd40954d2f7), with all the Debian goodness.


DataDirectory /var/lib/tor
PidFile /var/run/tor/
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


DisableNetwork 0 # only crashes going from 1 to 0, Opening Socks listener
ORPort 9001 # Crash when changed, OR listener
DirPort 9030 # Crash when changed, Directory listener
Sandbox 1

Child Tickets

Change History (1)

comment:1 Changed 6 years ago by nickm

Resolution: fixed
Status: newclosed

a056ffabbbdc76598830331c6550740a24fadeb8 should fix this one!

Note: See TracTickets for help on using tickets.