openssh unix dev - Dec 2002 - [Bug 459] ssh-keygen doesn't know how to export private keys

http://bugzilla.mindrot.org/show_bug.cgi?id=459

markus at openbsd.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From markus at openbsd.org  2003-01-01 03:40 -------
yes, but the manpage says that a PUBLIC key will be printed.




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=459





------- Additional Comments From markus at openbsd.org  2003-01-01 03:43 -------
you can however try to port putty's code for reading/writing ssh.com
private key files.


also note that the manpage says:

.Sq SECSH Public Key File Format

and there is no matching definition for _private_ keys.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=459





------- Additional Comments From cjwatson at debian.org  2003-01-01 04:46
-------
It does say that something will be printed in a public key format (although I
wasn't sure that the name of the format might not simply have been badly
worded), but the statement that it will read private OpenSSH key files is quite
confusing in this context. In fact, at least in the SSH2 case, it reads the
private key file, realizes it can't do anything with it, and then finds and
reads the public key file instead.

I'll have a look at the PuTTY code, or possibly just talk to Simon. :) I see
sshcom_write() here. Thanks.

Would you consider allowing this to be left open as an enhancement request? The
original bug reporter (Tomasz Cichecki <knight at kopernet.org>) said that
he
wanted to try out an ssh.com server without disturbing existing use, but was
unable to do so because he couldn't export the private key.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=459





------- Additional Comments From markus at openbsd.org  2003-01-01 23:15 -------
it's still possible to convert a private ssh.com key
to openssh format, but not vice versa. we don't
intend to provide support for migrating waway _from_ openssh




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=459

djm at mindrot.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED



------- Additional Comments From djm at mindrot.org  2003-01-02 11:58 -------
That being said - OpenSSH's protocol 2 keys are in a standard PEM format
which
you can dump out using "openssl rsa -noout -text -in .ssh/id_rsa"



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=459





------- Additional Comments From aet at cc.hut.fi  2003-01-05 09:56 -------
Created an attachment (id=193)
 --> (http://bugzilla.mindrot.org/attachment.cgi?id=193&action=view)
A quick hack to export unencrypted private keys

I noticed the lack of exporting private keys a few months ago and
therefore created the following patch to do the job. Should
work for all unencrypted RSA/DSA private keys.

I don't care if the patch ever goes to the main source tree,
there's still people who probably need the functionality
in ssh-keygen, so I might just as well share it.




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.