You're viewing a comment by Paul M. and its responses.

Paul M. Permalink
May 07, 2010, 17:55

If you're concerned about limiting access to your ssh pseudo-proxy and it's running locally, why not just have ssh bind to localhost, rather than 0.0.0.0?

Comment Responses

May 07, 2010, 18:11

For example, you want to give your friend socks5 access but you don't have root on the machine and you don't want everyone to have open access to it. Then as I described, you can start the socks5 proxy on, let's say, port 55555, and provide ip based access control via tcp-proxy.pl which would listen on port 0.0.0.0:1080 and forward requests to localhost:55555.

Reply To This Comment

(why do I need your e-mail?)

(Your twitter handle, if you have one.)

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

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