Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #16006

Closed (moved)
Open
Opened May 12, 2015 by Yawning Angel@yawning

torsocks should support isolating on a per process basis.

#16004 (moved) + #14132 (moved) would be the better way to handle this since it allows doing this for more than torsocks, but as something that can happen in the mean time (or if the user doesn't want to use AF_UNIX based SOCKSSocket), there's no reason that torsocks can't do this automatically.

Rough idea:

   IsolatePid 0|1

     Automatically set the SOCKS5 username/password to a unique per-process value
     that makes the connections to Tor use a different circuit from other existing
     streams on a per-application basis.  If set, the SOCKS5Username and
     SOCKS5Password options must not be set. (Default: 0)

The implementation would stash the pid/time(NULL) on startup and use pid:TIME (both ASCII serialized) as the SOCKS5 username/password pair for all SOCKS connections.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#16006