Re: Odd messages after upgrade
From: Stein Arne Storslett (sastorsl_at_THOU.SHALT.NOT.SPAM.broadpark.no)
Date: 08/31/05
- Next message: bruce ackman: "can anyone recommend a good ssh client for mac os 10.4?"
- Previous message: Stein Arne Storslett: "Re: ssh2 and scp2 fails in crontab."
- In reply to: Gushi: "Odd messages after upgrade"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 31 Aug 2005 10:45:11 GMT
<google@gushi.org> wrote in <1125402132.240790.223710@g49g2000cwa.googlegroups.com>:
> Hey all, I just upgraded to the latest 4.1-portable openssh, and now
> when trying to log into my system I get the following:
>
> danm@box:/etc/ssh$ ssh danm@prime.gushi.org
> WARNING: DSA key found for host prime.gushi.org
> in /home/danm/.ssh/known_hosts:1
This is what you should be looking at. In /home/danm/.ssh/known_hosts,
line 1 you have an entry for your server. When you installed the new
openssh you installed a new set of keys on the server. They then do not
match the old "fingerprint" you had in the ~/.ssh/known_hosts file.
> DSA key fingerprint d9:07:d0:eb:89:3d:04:73:33:e8:05:1c:6d:06:af:6b.
> The authenticity of host 'prime.gushi.org (65.125.228.130)' can't be
> established
> but keys of different type are already known for this host.
> RSA key fingerprint is ed:53:bd:52:65:9d:9d:9f:e8:bf:71:2a:82:03:1b:38.
> Are you sure you want to continue connecting (yes/no)?
>
> I have *always* had DSA *and* RSA keys available. Does the upgrade
> cause the server to offer the keys in a different order of some sort?
>
> Is there any way I can force the thing to go back to its old behavior?
>
> Is one key type inherently better than another for some reason?
-- Stein Arne
- Next message: bruce ackman: "can anyone recommend a good ssh client for mac os 10.4?"
- Previous message: Stein Arne Storslett: "Re: ssh2 and scp2 fails in crontab."
- In reply to: Gushi: "Odd messages after upgrade"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|