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
  • #20782

Closed
Open
Created Nov 26, 2016 by Yawning Angel@yawning

Use a seccomp whitelist when the tor daemon is configured to use Bridges.

The seccomp whitelist for the tor sandbox only has the system calls required for the tor daemon itself (based off tor's UseSandbox implementation). This causes obfs4proxy to not work, so when Bridges are enabled, a rudimentary blacklist is installed instead.

The proper thing to do would be to figure out what systemcalls obfs4proxy needs in addition to the ones in the current whitelist and selective expand the whitelist at runtime based on configuration.

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