Quote:
Originally Posted by
rafunk
To clarify, by public shell I meant a shell for which you can sign up on certain websites for free. You signup and then you can use your personal login and password to access the shell.
I understood exactly what you mean by a free shell account.
On these accounts, you don't have superuser permissions and you did not install and compile
sshd yourself. This means you don't know what sshd is doing.
In addition, when you set up an ssh connection between your client and the free shell server, only the connection is secure between the end points of the sockets.
This means that the superuser on the free server could, in theory, log and read your messages, if they wanted to with a simple code mod.
If you want "security" you need to have control over the "box in the middle" or you will be subject to a variation of what is called "the man in the middle attack".
Of course "secure" is relative, and if you don't care if the superuser on the free shell server can track your web surfing, then ...... it does not matter. I simply answered your question correctly, that it is not "secure" to use a third party server that you don't have superuser privs on the box.