Having trouble getting a key generated fo ssh2 on the commercial version
of secure shell to work on OpenSSH on a redhat 6.2 box.

The first thing I noticed is the commercial version has linefeeds in the
key.  Reading the ssh-keygen man page leads me to believe there is a
difference between the ssh2 spec and the openssh implementation since
there is a method ofnconverting keys back and forth.  From the man page:

<skip>
     ssh-keygen -x [-f input_keyfile]
     ssh-keygen -X [-f input_keyfile]
     ssh-keygen -y [-f input_keyfile]
     ssh-keygen -c [-P passphrase] [-C comment] [-f keyfile]
     ssh-keygen -l [-f input_keyfile]
<skip>

     -x      This option will read a private OpenSSH DSA format file and
print
             a SSH2-compatible public key to stdout.

     -X      This option will read a unencrypted SSH2-compatible private
(or
             public) key file and print an OpenSSH compatible private
(or pub
             lic) key to stdout.

     -y      This option will read a private OpenSSH DSA format file and
print
             an OpenSSH DSA public key to stdout.

I have tried various combinations to generated the open version of the
key but here is what I get:

 
[bhughes@compaq3 bhughes]$ ssh-keygen -Xf garytest.pub >
garytestopenssh.pub
ignore: ---- BEGIN SSH2 PUBLIC KEY ---- Comment: "testing [1024-bit dsa,
gfanning@bhughes, Fri Feb 02 2001 00:\ 19:54]"
AAAAB3NzaC1kc3MAAACBAIPyda2K/ySxdKHtRocRrNrJBI7BnhNsPEBzpuQmFYHzWEBdRA
qM08BV8rtci1iRyRHVuZizG2GX53Lw9QVFpNGTjzPbg07Di4Me656b+f4EJqNWISKW6z/1
5ZhtDxqtCWa3rGFuKJFY195DxfhU5CldDtj/gU5jqHnUz0CDQS3vAAAAFQCTB13MaRU9lZ
Vm0SKdP7Jx3zy5KwAAAIA28Zi/vKM+dFlNRT3O9Mf+VuTontPp8WX5VXyoy5YMWt7g1BW3
WBaV4qzAWo0Bloqg1HAusguCUfZLahgiB5h5Eg//5QmtZGQRToDSJHur3WeTXeQ1dxPlye
gd6UVyGrME60IkNpdjs1Ly0wpVFfJ6f8y9+g9g9L7uBm+I4Gp2pQAAAIAM+DXaU4GUNHSv
RP/8sGJFmg4LpvUlLOiED65GyALJgthMrHt+bHQGKAUfkdEoXsIxmiH5xmPQqb4ANwmVqN
D41G5AE9crmd7tisCSS/VvBS4meURR+AINjij4LLXkpNtLjWGiS9TyZwWrZbRjGobtW+F0
GrSK6V9u8D9T9PbXZQ== ---- END SSH2 PUBLIC KEY ----

the file garytestopenssh.pub remains empty :(  Ideas anyone?


Question:   Is the key generated by ssh an unencrytped key?

Question:  Where do I look fo more answers. Like who is out of spec
here.  I am always leaning toward screaming about those damn proprietary
vandors but I thought I would look before I leap for a change.


Any help or tips appreciated.

Bret



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to