Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#36808 closed defect (fixed)

tsocks: replace by torsocks?

Reported by: ryandesign (Ryan Schmidt) Owned by: sami.laine@…
Priority: Normal Milestone:
Component: ports Version: 2.1.2
Keywords: Cc: cm1@…
Port: tsocks, torsocks

Description

I'm not sure if I'm reading the tsocks and 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.

Change History (5)

comment:1 in reply to:  description Changed 8 years ago by sami.laine@…

Replying to ryandesign@…:

I'm not sure if I'm reading the tsocks and 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.

comment:2 Changed 8 years ago by ryandesign (Ryan Schmidt)

Resolution: fixed
Status: newclosed

A patch was supplied in #37363. I committed a simplified version in r100724, using the obsolete-1.0 portgroup instead of doing it manually.

comment:3 Changed 8 years ago 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...

comment:4 Changed 8 years ago by ryandesign (Ryan Schmidt)

Cc: cm1@… added

Resurrected! See #37666.

comment:5 in reply to:  4 Changed 8 years ago by cm1@…

Replying to ryandesign@…:

Resurrected! See #37666.

Thanks!

Note: See TracTickets for help on using tickets.