You're viewing a comment by Anon and its responses.

Anon Permalink
May 07, 2010, 13:38

SOCKS, besides being an abysmally awful protocol, is not supported by the majority of Internet software, so the advice you give is of limited usefulness. When I am confronted with a thoroughly hostile firewall, I depend on Net::Proxy. Accept no lesser substitutes.

Comment Responses

May 07, 2010, 18:13

On Linux you can LD_PRELOAD trick to make any software use a socks proxy. Socksify does that, also tsocks does that.

Net::Proxy indeed is a good one. Much better than my primitive tcp-proxy. But I wrote it out of curiosity, hadn't used IO::Socket and IO::Select in ages and wanted to refresh my knoweldge.

May 11, 2010, 21:07

If you want to make some SOCKS proxy available to all your applications, possibly better way than using tsocks is implementing iptables-based solution with the help of redsocks (git repository). See my tip Making SOCKS proxy transparent for example.

Another useful (in this context) ssh option is -g, but it requires turning GatewayPorts on in sshd_config.

Reply To This Comment

(why do I need your e-mail?)

(Your twitter name, if you have one. (I'm @pkrumins, btw.))

Type the word "network": (just to make sure you're a human)

Please preview the comment before submitting to make sure it's OK.