Odd messages after upgrade
From: Gushi (google_at_gushi.org)
Date: 08/30/05
- Next message: markus berges: "I cant authenticate a chrooted user"
- Previous message: Michael Laajanen: "Re: Another ssh problem - it looks up after a couple of minutes."
- Next in thread: Stein Arne Storslett: "Re: Odd messages after upgrade"
- Reply: Stein Arne Storslett: "Re: Odd messages after upgrade"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 30 Aug 2005 04:42:12 -0700
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
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?
Email to gushi at domain gushi.org is also helpful.
Thanks
- Next message: markus berges: "I cant authenticate a chrooted user"
- Previous message: Michael Laajanen: "Re: Another ssh problem - it looks up after a couple of minutes."
- Next in thread: Stein Arne Storslett: "Re: Odd messages after upgrade"
- Reply: Stein Arne Storslett: "Re: Odd messages after upgrade"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|