Check this out - https://www.browsershell.com Its a web based SSH client which allows you to access an SSH server through a web browser. Its just like opening up a terminal and connecting your remote machine. Very useful if you find yourself stuck behind a firewall which blocks SSH or you can't get a terminal or access to putty. enjoy :-)

nice, but i like http://webssh.50webs.com/ better. It's the same principle, but it's free.

I would not want to entrust a third party with either my username, my account's password, or my SSH private key. If you really need to circumvent a packet filter, set up a gateway machine that listens for SSH connections on port 80, or try tunnelling packets another sneaky way (as described on http://thomer.com/howtos/nstx.html for example). [Modified by: Johannes Truschnigg on June 18, 2008 08:16 PM]

[quote=nellynux]nice, but i like http://webssh.50webs.com/ better. It's the same principle, but it's free.[/quote] Thats free because it doesn't use SSL, far from secure!

[quote=Johannes Truschnigg]I would not want to entrust a thirs party with either my username, my account's password, or my SSH private key. If you really need to circumvent a packet filter, set up a gateway machine that listens for SSH connections on port 80, or try tunnelling packets another sneaky way (as described on http://thomer.com/howtos/nstx.html for example).[/quote] No need to trust them with your credentials, Unlike other web based ssh clients Browser Shell doesn't store any information about your server.

with EVERY web based ssh client (you might also want to take a look at www.gotossh.com, my.anyterm.org and www.serfish.com for example) your data goes in unencrypted form through their web servers - of course all of these service providers claim to [b]not[/b] log your data, still it is a question of trust. you have to be aware of that if you decide to use web based shell access. and of course SSL/HTTPS is a must. read the detailed notes on security on [url]http://www.serfish.com/console/web-ssh-security.jsp[/url] for example. similar discussions can also be found on www.gotossh.com and my.anyterm.org etc. only the promoted browsershell.com does not provide serious information on security which makes it kind of "suspect". btw: search google for free web based ssh clients and you might find free alternatives using ssl etc.

[quote=sana33]your data goes in unencrypted form through their web servers[/quote] This is not true, SSL provides the encryption between the client browser and the web server, the web server then passes that data directly to an SSH call. So long as the web server does not log, store that information it is secure. [url]http://www.browsershell.com[/url] is the only web based ssh client which does not store the user's credentials. If the web server is stoing your credentials then they must store them in plain so they can be passed to the ssh server. This means that [url]http://www.browsershell.com[/url] is the only truley secure web based ssh client. The security policy on [url]http://www.browsershell.com[/url] is quite clear, of course it is a matter of trust between the user and the owner of the web based system.

[quote=jj][quote=nellynux]nice, but i like http://webssh.50webs.com/ better. It's the same principle, but it's free.[/quote] Thats free because it doesn't use SSL, far from secure![/quote] It DOES use ssl, the link just points to a faq and in that faq you will find https links to the terminal.

[quote=jj] So long as the web server does not log, store that information it is secure. [/quote] if you like to consider this "secure", feel free. i hope the people reading this understand the risk of your server being hijacked, compromised, etc. so it is definitively a risk to send ssh data through a third-party tunnel. [quote=jj] ... is the only web based ssh client which does not store the user's credentials. [/quote] all of these web ssh providers do the same. read the policies of www.serfish.com or my.anyterm.org for example. so i really see no innovation there. (and neither do i see innovation in trying to post the url to your site three times a post :)) [Modified by: sana33 on July 13, 2008 06:42 PM]

[quote=sana33] if you like to consider this "secure", feel free. i hope the people reading this understand the risk of your server being hijacked, compromised, etc. so it is definitively a risk to send ssh data through a third-party tunnel. [/quote] So basically what you are saying is that a web based ssh server is more likely to get hijacked that the ssh server you are connecting to. Moot point really, It is no more or less likely to get targeted than any other server. So long as the web based ssh server owner takes the appropriate security measures like closing off ports, restricting access etc.. it is no more or less likely to get hit that your server. [quote=sana33] all of these web ssh providers do the same. read the policies of www.serfish.com or my.anyterm.org for example. so i really see no innovation there. (and neither do i see innovation in trying to post the url to your site three times a post :)) [/quote] Correct, they do the same, the client is just paying a small subscription fee to use the web server as a client. You could set up your own web based ssh server by implementing ajaxterm etc... but the point is that the web based ssh server is remote from all your other servers so should you loose access to them you can still reach them through a web browser. I have never suggested that is [url]http://www/browsershell.com[/url] anything else, it is just a web based ssh client. If you don't like it then don't use it and dont waste your time making boring comments about it if you've got nothing positive to say, I certainly see no innovation in that! [Modified by: jj on July 27, 2008 12:19 AM]