#36808: tsocks: replace by torsocks? -------------------------------+-------------------------- Reporter: ryandesign@… | Owner: sami.laine@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: Port: tsocks, torsocks | -------------------------------+-------------------------- Comment (by sami.laine@…): Replying to [ticket:36808 ryandesign@…]:

I'm not sure if I'm reading the [http://ima.udg.edu/~rgarcia/tsocks/ tsocks] and [http://torsocks.googlecode.com/ torsocks] homepages correctly, but it seems as though tsocks is obsolete and torsocks is its replacement. If that's true, then we should mark the tsocks port `replaced_by torsocks`. If I'm reading the homepages incorrectly, please feel free to close this ticket as invalid.

I think you're right, torsocks is at least intended to be tsocks replacement. -- Ticket URL: <https://trac.macports.org/ticket/36808#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS

#36808: tsocks: replace by torsocks? -------------------------------+-------------------------- Reporter: ryandesign@… | Owner: sami.laine@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: fixed | Keywords: Port: tsocks, torsocks | -------------------------------+-------------------------- Comment (by cm1@…): Unfortunately, it turns out torsocks is not a working replacement for tsocks for people like me who use tsocks with a simple SOCKS server. Apart from the fact that it doesn't allow to disable DNS forwarding (it fails with an error), it also contains hard-coded hacks which only work when used together with TOR, and even then are questionable. For example, I ran into a list of hard-coded IP network addresses which it refuses to open connections to because it's afraid something is trying to bypass the TOR network: 10:53:12 libtorsocks(63158): connect: Connection is to a local address (10.165.132.36), may be a TCP DNS request to a local DNS server so have to reject to be safe. Please report a bug to http://code.google.com/p/torsocks/issues/entry if this is preventing a program from working properly with torsocks. Looking at the code for torsocks, it appears the author is completely focused in TOR use, hard-coding bits and pieces all over the place without adding configuration options, etc. I guess it would be more work to fix torsocks than simply keeping tsocks alive... -- Ticket URL: <https://trac.macports.org/ticket/36808#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS

#36808: tsocks: replace by torsocks? -------------------------------+-------------------------- Reporter: ryandesign@… | Owner: sami.laine@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: fixed | Keywords: Port: tsocks, torsocks | -------------------------------+-------------------------- Comment (by cm1@…): Replying to [comment:4 ryandesign@…]:

Resurrected! See #37666.

Thanks! -- Ticket URL: <https://trac.macports.org/ticket/36808#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS