Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #18633

Closed (moved)
(moved)
Open
Created Mar 25, 2016 by cypherpunks@cypherpunks

Tor service crashes on Debian sid when seccomp enabled in torrc

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.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking