Slashdot Mirror

How about a web - based ssh client like http://www.appgate.com/products/80_MindTerm/ ? You drop the jar somewhere voilà, instant ssh connection on a browser that has java.

Disclamer: I _dont't_ work for said company, just a very satisfied user.

If you run MindTerm (http://www.appgate.com/products/80_MindTerm/, Java applet SSH) with tunneling, and you have the java applet enabled on a VNC session internally, you can view everything local to your server instead of having to pull it across to the local machine. The utility value varies with the type and size of the attachment, but I like being able to securely remote VNC from any web browser.

Derek

I'm sure i've seen a java ssh client, that you use in your browser..

You are probably thinking of MindTerm. If you don't have a web server you can stick it on, Google has some hits of existing installations that will work.

It is able to do most of the things you need. It all depends on how complex solution you want.

Mindterm.

Instead of fixating on "this one's integrated with KDE" and "this one allows profiles so you can keep your color choices", Mindterm allows SSH access from any computer with a Java-enabled browser. In many ways, that's more useful to me than the differences between the reviewed terminal emulators.

When I'm at the console, a terminal is a terminal. My choice of shell makes a bigger difference to me. When I'm not at the console, it's easier to find a Java enabled browser than someone willing to let you install Putty (if it's a Windows box).

Instead of deciding which jewel-studded hammer you'd prefer to use, I'm much more interested in the hammer that does the job but is easier to carry around or fits on my belt.

All of the above issues are turning the Web into a mish-mash of unreadable, un-navigable garbage. If enough people refuse to stay on badly designed sites, the sites will die. Eventually, practices will change--hopefully.

Bull. Bad UI decisions have turned the Web into this. Bad UIs can be found everywhere, not just in the Web. That's what UI specialists are for. Just because you're a coder who hates Flash doesn't make you the cat's meo

Also check if the product supports the authentication method you want to use. This should normally not be a problem but since authentication systems may cost quite a lot it is a good idea to check it out.

Another thing to look at is reliability. How stable is the box, what happens if the box breaks? Can you connect multiple boxes in a cluster?

Also do not stare blindly at the SSL protocol but rather focus on functionality. There are other products which have similar functionality but builds on different protocols. For example AppGate which uses SSH as the basic protocol (disclaimer: I work for AppGate:-).

The most common functionalities people tend to look at are:

• The ability to have fine grained access control, down to the user level.
• Ease of deployment
• Ease of use
• "Network ruggedness" these products typically only rely on simple TCP streams so they have a higher success rate than IPsec in some network environments.

every cell fone should have a SSH client and a IP address. Being a Sys Admin, I know how important it is to get access to SSH.
If you can create a SSH tunnel (see mindterm through your your company's firwall, you can get to any intranet server using SSH on your cellfone
Or you could even SSH tunnel into your cell, and retreive telefone number, addresses(or other data).

Swedish company AppGate develops a commercial software that enables SSH-tuneled access to intranets for Ericsson P800 cell phones.

do a google on "mindterm ssh". it's a java applet that does ssh (1, maybe 2 as well, been a while since i looked at it) and vt100. it'll only connect (by default, this is a jvm thing) to the host it came from, but it's handy if you have a user base that may be "floaters" (i.e. may be on random machines traveling around; all they need is a web browser). ah, here's the link and it does support ssh2. it is free for "personal and limited commercial" use.

If you just need vt100/telnet style access (say, within your firewall'd lan) you might like ShellInABox, which is a GPL'd java applet shell for that purpose.

This has already been done, and better (with SSH support, to boot).

Apparently not very hard.

We run this on a server that a group of people I'm associated run. Works extremely well if you're on a box that doesn't have an ssh client installed.

I know that this is offtopic, but I can't help but be grateful that I can use pine over a ssh connection when I see articles like this. I can access all of my mail from nearly anywhere in the world and have the same capabilities as if I were sitting at my desk. I can even access it using only a java-enabled web browser using mindterm.

Has anyone seen a good Java applet for ssh access?

Mindterm looks pretty good, and would make it pretty easy to get at your email from whereever. It's covered by a proprietary public source license.

Also, their Java ssh client Mindterm kicks ass, but they have been changing their licensing several times the last year.

And also AppGate

mindterm ssh from appgate.com takes a novel approach to sftp. in addition to having a popup window that will do the sftp, you can also use the ssh client as an ftp proxy server - meaning you can use standard ftp to the ssh client, and it will then translate that into sftp to your ssh server. meaning you can have your users use whatever ftp client they like.

What you need is to combine VNC with a distributed (ie. multiple-computer, at multiple-locations, with multiple-ISPs on multiple-backbones) setup. I'm not aware of any automated products for this, what I've done in the past is to have an main CVS repository on one box, and a cron-job that updates it every night from a different machine. If you lose that main box, you'll have a worst-case day old copy of the repository on the other machine, and can still continue to do your work. If it's a big problem with several days of downtime, you can then set the backup as the main CVS server.

This could work for any number of "backup" computers, but even having two will pretty much eliminate the downtime you've suffered before. And you can use CVS to backup all sorts of stuff (code, IDE config files, even binary data).

In the *nix world, esp. if you're used to a command-prompt instead of a GUI, using VNC is often overkill - I tend to use an OpenSSH java applet (such as AppGate's excellent MindTerm), which can run over slow connections without issue, and can be served from any number of computers.

(However, for a Wintel solution, you'd have to find a configuration-management tool that can automatically update stuff for you - not sure if Source-Safe or StarTeam can do this).

What you need is to combine VNC with a distributed (ie. multiple-computer, at multiple-locations, with multiple-ISPs on multiple-backbones) setup. I'm not aware of any automated products for this, what I've done in the past is to have an main CVS repository on one box, and a cron-job that updates it every night from a different machine. If you lose that main box, you'll have a worst-case day old copy of the repository on the other machine, and can still continue to do your work. If it's a big problem with several days of downtime, you can then set the backup as the main CVS server.

This could work for any number of "backup" computers, but even having two will pretty much eliminate the downtime you've suffered before. And you can use CVS to backup all sorts of stuff (code, IDE config files, even binary data).

In the *nix world, esp. if you're used to a command-prompt instead of a GUI, using VNC is often overkill - I tend to use an OpenSSH java applet (such as AppGate's excellent MindTerm), which can run over slow connections without issue, and can be served from any number of computers.

(However, for a Wintel solution, you'd have to find a configuration-management tool that can automatically update stuff for you - not sure if Source-Safe or StarTeam can do this).