Comment 3 for bug 15359

> On 4 Jul 2002, Jonathan Amery <email address hidden> wrote:
> > You said:
> > > I'll make sure no machine still has the corresponding public key, and
> > > then send it through to you. Shall I just send it to you as an email
> > > attachment?
> >
> > Yes, that should be fine.
>
> OK, here they are. On my machine, I get:
>
> > mbp/2 sshkey-danger$ ssh-keygen -p -f ssh_host_key
> > cipher_encrypt: bad plaintext length 337
> > mbp/2 sshkey-danger$ ssh -V
> > OpenSSH_3.4p1 Debian 1:3.4p1-2, SSH protocols 1.5/2.0, OpenSSL 0x0090604f
>
> The key was generated with Debian's version of OpenSSH a few months
> ago. It was apparently working properly (i.e. could log in over
> sshv1) until the 3.4 upgrade.
>
 Hmm, I tried this on a stable machine here, and got the same error:

allison.empire.pick.ucam.org:~/ # [02/07/16.02:06:12] $
: pts/6 bash[4621] ; ssh-keygen -p -N '' -f key1
cipher_decrypt: bad ciphertext length 337
allison.empire.pick.ucam.org:~/ # [02/07/16.02:06:16] $
: pts/6 bash[4622] ; dpkg --list ssh
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
ii ssh 1.2.3-9.4 Secure rlogin/rsh/rcp replacement (OpenSSH)

 Do you have an extant backup of the host key from before the upgrade?
I fear that it might have got corrupted somewhere.

 Jonathan.