Quote: Originally Posted by DextrousDave
Quote: Originally Posted by logicearth
Umm...that is not going to make anything more or less secure. SSH is for creating secure connections to remote systems. (Mainly for administrating)
One more thing: Let's say I am in a public WiFi hotspot, and I connect to my SSH server located elsewhere, I can use that SSH server as a proxy server in my browser, so any browser traffic(packets) between my client PC on the public WiFi and the SSH server will be secure right? And also, I assume that setting up such a remote secure connection is basically the same as Windows native remote desktop connection?
Yes, it's a good idea to use such a setup. In fact, all the WiFi traffic goes encrypted this way, and then from the server to the web, unencrypted (you can't really avoid that unless using sites with HTTPS only).
It has nothing to do with the normal remote desktop. SSH is all about opening a remote command window in the server, SFTP and port forwarding (you'll be using the latter), but not a full control of the remote server. You can forward the port that terminal server uses (3389) to gain access in addition to the web proxy, but it's a whole different history. Also, the SSH protocol is specifically designed to be highly secure and with a very strong encryption, opposed to the remote desktop that has a relatively basic one in comparison.