The starting point of information on Secure SHell (SSH) is available from The Secure ShellTM Frequently Asked Questions
There is SSH2 now which is more secure than SSH (now known as SSH1).
I'm using the Linux port of the OpenBSD version of OpenSSH (currently v2.9p2-1) since it supports SSH versions 1.3, 1.5 and 2.0. It also has better public licensing restrictions and I don't want to have to reconfigure my server if I ever go into business operations. It also has Secure FTP SFTP. And it came with RedHat v7.0.
OpenSSH also requires the following packages:
Zlib (I'm running v1.1.3)
OpenSSL: v0.9.5a or greater (I'm running v0.9.5a) Currently v0.9.6a is available, but I don't feel like installing it yet. RPMs of OpenSSL are available. There are many extensions available to OpenSSH. Check them out.
The Main OpenSSH website:
The OpenSSH Mailing List has been archived and put in searchable form.
OpenSSH related mailing lists - subscribing, etc.
Basically, I just downloaded the RPMs and installed them overwriting the already installed version. The installation instructions from OpenBSD were a touch confusing to me. However, I'm a bit of a newbie to the OS.
Making keys and what not was a little confusing, but I figured it out. You need a host key on the host and it needs to be made without a passphrase or it won't load up. The keys are stored in /etc/ssh and there are one for each protocol and version (or you can remove them if you don't want to allow that protocol). If you've installed RedHat Linux 6.2 or later (maybe earlier, too), and installed OpenSSH, then it should have been done already, so you don't need to unless you really want to.
To make a key, login to linux under the username you want to generate a key
for. Issue the command ssh-keygen and press enter. You'll have to
enter a challenge phrase (twice), and allow it to dump the private key and
public key in the default places. You'll give the private key ($HOME/.ssh/identity)
to the user. If they lose the passphrase, you'll have to regenerate the key as
there is no good method of recovering the passphrase. You append identity.pub
onto the end of the authorized_keys file, creating the file if it's not already
made. Then you should be able to make it work.
Tera Term Pro, as of v2.3 is not SSH2 capable so I've decided to look for another client to deal with that. Although, if you use Tera Term Pro, then you need the Tera Term Pro SSH plug-in TTSSH.
last updated: 07/02/01 21:05:48 -0500