Wow. This this is the worst technology advice I've seen in a while:
http://getfoxyproxy.org/sshproxy.html
It amounts to suggesting you run an unrestricted SOCKS proxy public on the internet without any form of authentication.
The only real saving grace is that OpenSSH's dynamic SOCKS proxy support requires, you know, being connected to a remote SSH server. Thus by putting in "www.paypal.com" you'll never actually connect (unless PayPal has been running some sort of unauthenticated SSH service that I've never heard of).
OpenSSH's dynamic SOCKS proxy feature is awesome, but you really need to be running a SSH server to relay the traffic through. Just make sure you use a strong password or public key authentication. You can even run it on a non-standard port like 443 if you're worried about overzealous outbound firewalls.
http://getfoxyproxy.org/sshproxy.html
It amounts to suggesting you run an unrestricted SOCKS proxy public on the internet without any form of authentication.
The only real saving grace is that OpenSSH's dynamic SOCKS proxy support requires, you know, being connected to a remote SSH server. Thus by putting in "www.paypal.com" you'll never actually connect (unless PayPal has been running some sort of unauthenticated SSH service that I've never heard of).
OpenSSH's dynamic SOCKS proxy feature is awesome, but you really need to be running a SSH server to relay the traffic through. Just make sure you use a strong password or public key authentication. You can even run it on a non-standard port like 443 if you're worried about overzealous outbound firewalls.
