torsocks should support isolating on a per process basis.

[yawning]

#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.

[yawning]

​https://github.com/Yawning/torsocks/compare/bug15584...bug16006

Based on top of my #15584 branch since I changed a bunch of the init stuff, and can't be bothered untangling it/dealing with merge conflicts (since I run with #15584 fixed on all my boxes).

Differences from the description:

• Username is torsocks- PID : time(NULL)
• Password is 0 (To allow for new circuit hackery later, this is how Tor Browser does it).

The SOCKS5 Username/Password isn't currently being sent for RESOLVE and RESOLVE_PTR requests either, so that's fixed in my branch as well (as a separate commit for cherry picking).

[dgoulet]

I added a command line option to trigger this feature. See -i/--isolate.

Merged! thanks