Troubles with SSH

[freddieB]

Trying to install SSH onto a RH6.2 box. Got the RPM and got it starting to install. Then I get the following message:

ssh ################################################## Hostkey found at /etc/ssh2/hostkey, not regenerating.
Assuming RedHat Linux compatible and trying to configure...
Configuration seems to have failed. You might be running other than RedHat.
Please edit configuration files by hand.
Please make sure you haven't specified sshd in /etc/rc.d/rc.local

If you already have sshd running, you should restart it or reboot.
Configuration done.

What have I done wrong? I had previously tried to install from the tarball, but that went equally as well.

[mclewson]

I had nothing but problems with the ssh rpm. I found a copy of the source code. The compile and install was a piece of cake. I highly recommend going that route.
Mclew

[SKoL]

On the other hand..

I've ONLY used SSH RPM's for RedHat and it was easy. I installed SSH, SSH server, SSH client, and SSH extras. Kicks ***, not ONE problem.

------------------
---=== SYSTEM RULES ===--
1. Do not post crap
2. Obey rule #1
3. Only post stuff that rule #2 allows

[Bill]

Get it from ftp.ssh.com and compile it yourself. It only takes a few minutes.

------------------
Did I do that?

[jesterspet]

I vote for the "Hard way" (install from source).

I have installed and run both SSH and SSH2 and got both to run and accept/establish connections. SSH was the first thing I actually tried to install from source and was a real learning expierence.

The only reason I removed SSH was to try the "uninstall" process. Again a learning expierence. It was so painless I went through it 3 times just to make sure I got all the options and stuff I wanted in the install, and to ensure I actually got everything removed.

Experment with SSH1 first and then go to SSH2. Some how on my last install of SSH2 I got it running in a unique way. When ever I want a SSH conection, I type ssh <username>@host and it will try to establish a SSH2 connection, If it fails and needs a SSH1 connection, it drops down to SSH1 compatability, issues a warning about it, and then connects. The same goes for the reverse, IF I try to connect from a machine that only has SSH1 installed, sshd will drop to compatability mode and accept the connection. It is pretty cool, everyone that I know that runs SSH & SSH2 have to specify which version of SSH they want to use (ssh or ssh2) when establishing a connection.

If you duplicate what I have done post it to the discussion, as I have not figured out how I did it. http://www.linuxnewbie.org/ubb/redface.gif

It is my understanding that this is not possible with a RPM install, as well as enabling tcpwrappers. but I could be wrong. http://www.linuxnewbie.org/ubb/biggrin.gif

------------------
[X] YES! I'm a brain-damaged lemur on crack, and I'd like to order your software package for $459.95!