Subject: Re: [libssh2] Libgcrypt port update

Re: [libssh2] Libgcrypt port update

From: Mononen Jussi <>
Date: Thu, 18 Jan 2007 15:51:33 +0200

>> > I have just started to write it, so there isn't much to
>> share yet. I can
>> > post it when I'm done.
>> Yes, that would be very useful! With that, I could convert
>> my OpenSSH
>> key to SECSH format using ssh-keygen, and then use it to debug the
>> remaining part of libssh2 for the libgcrypt port. PEM file
>> reading is
>> boring to write, so I'd like to procrastinate on that for a while.

I'll post it when I'm done. Currently I am doing it within the
libssh2_file_read_publickey -function.

>> Is there a standard on what the SECSH filenames are?

AFAIK there are no restrictions, so far I have seen various version
containing more or less host/user/strength information in the filename.

>> Is it wise to have the libssh2 public-key-file reader
>> support both formats in the same file?

I can't see any harm, instead it will allow users to send SECSH
formatted public key to a server requiring during authentication.

>> I wonder why OpenSSH doesn't support the SECSH format in 'ssh'...

Me too.


Disclaimer: This message and any attachments thereto are intended solely for
the addressed recipient(s) and may contain confidential information. If you
are not the intended recipient, please notify the sender by reply e-mail and
delete the e-mail (including any attachments thereto) without producing,
distributing or retaining any copies thereof. Any review, dissemination or
other use of, or taking of any action in reliance upon, this information by
persons or entities other than the intended recipient(s) is prohibited.
Thank you.

Take Surveys. Earn Cash. Influence the Future of IT
Join's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
libssh2-devel mailing list
Received on 2007-01-18