Re: ssh reports identification change when key has not been changed

From: John Leonard (johnleonard@e-merge.ie)
Date: 06/28/02


From: johnleonard@e-merge.ie (John Leonard)
Date: 28 Jun 2002 12:36:09 -0700

Simon Tatham <anakin@pobox.com> wrote in message news:<LbE*GvMrp@news.chiark.greenend.org.uk>...
> John Leonard <johnleonard@e-merge.ie> wrote:
> > The thing is, I didn't (nor did anyone else) change the host public
> > key. If I log on to the problem machine and type:
> > # ssh-keygen -l -f /etc/ssh_host_key
> > I get:
> > 1024 b4: ... let's call it ALPHA
> > Which is the original key.
>
> It might be worth checking that /etc/ssh_host_key really is the key
> being used by the SSH server. For example, it's not impossible that
> one of those patches you installed might have included an SSH server
> configured to read its key from somewhere different (for example,
> /etc/ssh/ssh_host_key springs to mind). This would explain why
> typing that command shows you the old key but actually connecting to
> the server shows the new key.

Sorry it took so long for me to reply. Thanks for replying, you were
right, the keys were actually in /usr/local/etc - the default after
version 3 I guess.

I just copied the keys from /etc to there and the previous warnings
were gone.

>
> > Just as a test, I'm not sure this is even valid, I tried to ssh into
> > the problem server FROM the problem server. This reported a different
> > key, GAMMA.
>
> This might be because SSH1 and SSH2 use separate keys. Check that
> key GAMMA is for the same version of the protocol as ALPHA and BETA.

Right again. GAMMA was in the dsa key file, protocol 2.

Thanks a million,
   John.



Relevant Pages

  • Re: ssh reports identification change when key has not been changed
    ... > being used by the SSH server. ... > key GAMMA is for the same version of the protocol as ALPHA and BETA. ... GAMMA was in the dsa key file, protocol 2. ...
    (comp.security.ssh)
  • Port Assignment- OT in a Small Way
    ... 5:RJE - Remote Job Entry ... 18:MSP - Message Send Protocol ... server, Traitor 21, WebEx, WinCrash, NerTe, ... 22:SSH - SSH Remote Login Protocol, RAT: Shaft ...
    (comp.security.misc)
  • Port Assignment- OT in a Small Way
    ... 5:RJE - Remote Job Entry ... 18:MSP - Message Send Protocol ... server, Traitor 21, WebEx, WinCrash, NerTe, ... 22:SSH - SSH Remote Login Protocol, RAT: Shaft ...
    (comp.security.firewalls)
  • Port Assignment- OT in a Small Way
    ... 5:RJE - Remote Job Entry ... 18:MSP - Message Send Protocol ... server, Traitor 21, WebEx, WinCrash, NerTe, ... 22:SSH - SSH Remote Login Protocol, RAT: Shaft ...
    (alt.computer.security)
  • PORT NUMBER AND SERVICES
    ... 5:RJE - Remote Job Entry ... 18:MSP - Message Send Protocol ... server, Traitor 21, WebEx, WinCrash, NerTe, ... 22:SSH - SSH Remote Login Protocol, RAT: Shaft ...
    (comp.security.firewalls)