Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 343
    • Issues 343
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 35
    • Merge requests 35
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #18397
Closed
Open
Issue created Feb 26, 2016 by Trac@tracbot

`Sandbox 1` in Tor 0.2.7.6 should not filter `getsockopt` syscall

In Tor version 0.2.7.6 (git-605ae665009853bd) on Debian sid, setting Sandbox 1 in torrc filters the getsockopt syscall, which is necessary for applications such as torsocks, xmpp-client, and TorBirdy. This syscall should be re-un-blacklisted from the seccomp policy. I say 're' because I confirmed it works in Debian Jessie running version 0.2.7.6-1~d80.jessie+1.

Trac:
Username: fowlslegs

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