[itistoday]

Hi, using the campus network makes me feel paranoid that someone's sniffing all my traffic. There are several websites that I have to login to and my password is sent in the clear for them, so to secure these connections I'd like to use SSH tunneling. I already secure my SMTP using this method, however, in that case I connect to a specific port at a specific destination using this command:

Code:
ssh -N -p 22 -c 3des myuser@myremoteserver.com -L 10025/localhost/25

Could I just modify that to this to secure all my web connections:

Code:
sudo ssh -N -p 22 -c 3des myuser@myremoteserver.com -L 80/localhost/80

The thing is that I don't really have a strong grasp on what that command does. I believe the SMTP command that command tells it to login securely and to my remote server onto its ssh port, and then redirect traffic to localhost on port 10025 to the remote host's SMTP port.

Running the second command seems to work as expected, and web connections do work (except for some reason it requires me to type in my password, unlike the first, which is odd since I have 3des public/private keys on my local box and the remote machine, and because of that it doesn't ask for my password when I do SMTP tunneling).

Other than that, the second command for HTTP tunneling seems executes, but I don't know if it's actually working. If my interpretation of the SMTP command is correct, then it wouldn't make sense to forward traffic from my machine's request's to port 80 to the remote machine's port 80.


Essentially, am I doing it properly (probably not), and if not then how do I do it?


Edit: Or I might have to make a proxy with the -D option with ssh. I've tried doing this by following guides online by using this command:

Code:
/usr/bin/ssh -N -p 22 -c 3des -D 1080 myuser@myremoteserver &

And configuring my web browsers to use localhost:1080 as the proxy, but that didn't work, and I was unable to access any website.