#32877 closed defect (duplicate)

Sandbox crash when reloading log configuration

Reported by: pege Owned by:
Priority: Medium Milestone:
Component: Core Tor/Tor Version: Tor:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


A sandbox related crash was reported on the tor-relay mailing list. I'm currently looking into the issue and I expect to have a fix ready soon.

Original report:

Subject: [tor-relays] tor crash on HUP only when SANDBOX is 1
Date: Sun, 5 Jan 2020 07:43:45 +0100
From: tor-relay@...
Reply-To: tor-relays@…
To: tor-relays@…


I'm running an exit relay on a Debian Buster. I installed libseccomp and I've built tor using debuild, like the wiki says.

Today I noticed that tor crashes on HUP signal, only when the Sandbox option is on. I never had this problem.

This is what my log says:

an 05 08:23:10.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Jan 05 08:23:10.000 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Jan 05 08:23:10.000 [notice] Read configuration file "/etc/tor/torrc".
Jan 05 08:23:10.000 [notice] Tor opening log file.

============================================================ T= 1578205390
(Sandbox) Caught a bad syscall attempt (syscall dup)

I'm telling you because i think it could be a bug, but I'm not sure that It's not caused by something else.

At the moment I've disabled Sandbox. Please, let me know if I can fix this in some way, thanks.

Child Tickets

Change History (2)

comment:1 Changed 10 months ago by pege

The crash was caused by a call to dup() introduced in v0.4.1.7 as part of commit a22fbab98690f802ae3bda276078cc7fc767feba.

I created a patch at https://gitlab.com/pgerber/tor/commits/seccomp-dup that allows dup() to be used in the sandbox.

comment:2 Changed 10 months ago by nusenu

Resolution: duplicate
Status: newclosed

duplicate of #32841

Note: See TracTickets for help on using tickets.