Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'SOCKS 5, Making SOCKS optional, and cool things' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
SOCKS 5, Making SOCKS optional, and cool things
Authored by: CarlosD on Jul 14, '03 05:20:18PM

I have been using this for quite a while and it works quite well. I would amend this hint by letting you know that it does work for SOCKS v5 as well -- just use -5 instead of -4 in the configuration file.

Also, better than putting the ProxyCommand in the default config, create a copy of the config (called ssh_config.socks, say) with the ProxyCommand line. This way you have the option of specifying that you wish to use socks in the command line itself using the -F (config file) switch. (Or make the *copy* the non-socks version if you expect to be using ssh more outside the firewall.)

For example, you can do something like this:

ssh in-house-host.mycompany.com
# uses the default, non-socksified config

ssh -F /etc/ssh_config.socks outside.host.com
# uses your modified config via the SOCKS server

Combined with dynamic dns or a static IP, you can do things with your machine from almost anywhere. What's *really* cool is when you combine this with tunneling (the -L switch) and VNC: free, secure, encrypted, global remote control.



[ Reply to This | # ]