[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-bugs] #18633 [Tor]: Tor service crashes on Debian sid when seccomp enabled in torrc



#18633: Tor service crashes on Debian sid when seccomp enabled in torrc
-----------------------------+--------------------------
     Reporter:  cypherpunks  |      Owner:
         Type:  defect       |     Status:  new
     Priority:  Medium       |  Milestone:
    Component:  Tor          |    Version:  Tor: 0.2.7.6
     Severity:  Normal       |   Keywords:
Actual Points:               |  Parent ID:
       Points:               |   Reviewer:
      Sponsor:               |
-----------------------------+--------------------------
 I'm having issues with setting "Sandbox 1" in torrc on Debian sid. When I
 do, the process crashes and restarts indefinitely.

 I see two suspect log entries, one from my auditd log, one from tor log.

 First auditd:

 type=SERVICE_START msg=audit(____): pid=1 uid=0 auid=____ ses=____
 msg='unit=tor@default comm="systemd" exe="/lib/systemd/systemd" hostname=?
 addr=? terminal=? res=failed'

 And here is a suspect tor log entry:
 (Sandbox) Caught a bad syscall attempt (syscall getsockopt)

 Not entirely sure what is causing the issue. I also have apparmor enabled
 and enforced with the default system_tor profile, but I'm not seeing any
 denials being logged, so I'm assuming apparmor is not at fault.

 The process restarts rapidly when this happens -- it exits and starts over
 and over. When I do one "ps aux | grep tor" to find the pid, then "pgrep
 tor" to confirm, and expect to look in /proc/(pid) to confirm sandboxing
 is enabled... the pid has already changed.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/18633>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs