Hi,
I am running openssh7.3p1 on an embedded Linux system and discovered this
problem.
If I run:
ssh-keygen -t rsa1 -f testfile
it appears to generate the key and I get the output:
Generating public/private rsa1 key pair.
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Saving key "testfile" failed: unknown or unsupported key type
Should this option be returning with a deprecated key type message ?
I can't find a bug already reported about this and I have downloaded openssh
7.4p1
and the problem exists on that too. I have checked the archives at
http://marc.info/
and there didn't appear to be anything there.
Apologies if this has apready been discussed as I am not on the mailing list.
Thanks in advance for any pointers
Kelly
--
Kelly Dunlop
kdunlop at guralp.com
Guralp Systems Limited
http://www.guralp.com
On Wed, Feb 15, 2017 at 9:50 PM, Kelly Dunlop <kdunlop at guralp.com> wrote:> > > Hi, > > I am running openssh7.3p1 on an embedded Linux system and discovered this problem. > > If I run: > > ssh-keygen -t rsa1 -f testfile > > it appears to generate the key and I get the output: > > Generating public/private rsa1 key pair. > Enter passphrase (empty for no passphrase): > Enter same passphrase again: > Saving key "testfile" failed: unknown or unsupported key type > > Should this option be returning with a deprecated key type message ?It looks like a bug. git bisect points at 2aa9da1a3b360cf7b13e96fe1521534b91501fb5 is the first bad commit commit 2aa9da1a3b360cf7b13e96fe1521534b91501fb5 Author: djm at openbsd.org <djm at openbsd.org> Date: Tue Mar 24 01:29:19 2015 +0000 upstream commit Compile-time disable SSH protocol 1. You can turn it back on using the Makefile.inc knob if you need it to talk to ancient devices. That said, we're about to remove SSH1 support in the client (it's already gone from the server) so I'm not sure this is is ever going to be fixed... -- Darren Tucker (dtucker at zip.com.au) GPG key 11EAA6FA / A86E 3E07 5B19 5880 E860 37F4 9357 ECEF 11EA A6FA (new) Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement.
On Fri, Feb 17, 2017 at 9:25 AM, Darren Tucker <dtucker at zip.com.au> wrote:> git bisect points at > > 2aa9da1a3b360cf7b13e96fe1521534b91501fb5 is the first bad commit... and if I'd actually looked at the change itself: - [ --without-ssh1 Disable support for SSH protocol 1], + [ --with-ssh1 Enable support for SSH protocol 1], so yeah, ssh-keygen should have probably errored out "unsupported key type". -- Darren Tucker (dtucker at zip.com.au) GPG key 11EAA6FA / A86E 3E07 5B19 5880 E860 37F4 9357 ECEF 11EA A6FA (new) Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement.