Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • 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
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #13716

Tor daemon apparmor profile breaks bridge restarts on Ubuntu 14.04

As intrigeri noted here https://trac.torproject.org/projects/tor/ticket/9460#comment:13 a new apparmor mediation for signals in 14.04 breaks tor being able to kill obfsproxy on restart (meaning it comes up without obfsproxy since the old process continues holding on to the open port.) Example syslog: type=1400 audit(1415580423.404:19): apparmor="DENIED" operation="signal" profile="system_tor" pid=4514 comm="tor" requested_mask="send" denied_mask="send" signal=term peer="unconfined"

He also mentioned that adding the correct rule would break Debian, so an Ubuntu-specific fix was needed.

The rule that needs to be added is: signal (send) set=("term") peer="unconfined",

Not sure if the easiest path is to wait out Debian upgrading, updating Ubuntu packages, or adding an Ubuntu specific install line in Tor's apt package

Trac:
Username: vladtsyrklevich

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