[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #16006 [Torsocks]: torsocks should support isolating on a per process basis.
#16006: torsocks should support isolating on a per process basis.
-------------------------+-------------------------
Reporter: yawning | Owner: dgoulet
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Torsocks | Version:
Keywords: isolation | Actual Points:
Parent ID: | Points:
-------------------------+-------------------------
#16004 + #14132 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.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/16006>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs