1837202 Members
1954 Online
110115 Solutions
New Discussion

ssh 3.2.3p1 key problems

 
Sergio Crespo
Advisor

ssh 3.2.3p1 key problems

Hi

I've removed our 2.5.1p1 openssh version from our system. In all hpux 11i I add no problems in installing 3.2.3p1.
Now I'm doing the same to some Hpux 11.00 systems, and I'm getting a lot of problems.
First i started getting the "Could not load" message for protocol 1, I've created then the RSA1 key for the host. Now I'm getting the following message:
bash-2.03$ ssh host1
Warning: the RSA1 host key for 'host1' differs from the key for the IP address '192.111.11.113'
Offending key for IP in /home/src/.ssh/known_hosts:47
Matching host key in /home/src/.ssh/known_hosts:50
Are you sure you want to continue connecting (yes/no)? yes

If I choose yes, I'll connect to the machine.
I've tried to take out from the known_hosts file the entries for this machines, but I'm still getting the same.

Any Ideas?

Thankx in advance!!
SRBC
3 REPLIES 3
harry d brown jr
Honored Contributor

Re: ssh 3.2.3p1 key problems


Why not use 3.10 (3.1p1), I realize it's a "backrev" from 3.2.3p1, but at least the corresponding libraries are included?

http://www.software.hp.com/cgi-bin/swdepot_parser.cgi/cgi/displayProductInfo.pl?productNumber=T1471AA

live free or die
harry
Live Free or Die
Craig Rants
Honored Contributor

Re: ssh 3.2.3p1 key problems

You need to uncomment the type of key that you are using in your sshd_config file, if it doesn't know where to find the key, it can't load them at daemon start time.

GL,
C
"In theory, there is no difference between theory and practice. But, in practice, there is. " Jan L.A. van de Snepscheut
Sergio Crespo
Advisor

Re: ssh 3.2.3p1 key problems

Hi ... :)))
Thankx for your support, it is always welcome.
In fact the problem was really in the Known_Hosts entry. I removed the entry refering to the host, but I didn't realize that I had another entry with IP number of the machine.This is an offending key due to the facto of having to entries for the same machine with 2 different fingerprints.
In fact ssh 3.2.3p1 with tcp wrappers, didn't recognize my acient RSA1 key, and I just created another one.
After creating new RSA1 Key, i just did a cat /dev/null > /home//.ssh/known_hosts and solved the problem.
SRBC