Subject: Re: [libssh2] Libgcrypt port update

Re: [libssh2] Libgcrypt port update

From: Mononen Jussi <>
Date: Thu, 18 Jan 2007 14:56:23 +0200

>> Let me know if you have any comments or thoughts on the code, my
>> approach, or whatever.

Hi Simon (and others),

while you are working your way through the PEM file reading would it be
possible to add support for SECSH formatted public keys in userauth.c?

I am about to make modifications to libssh2 version 0.12 in order to use
SECSH formatted public key (OpenSSH vs. Tectia issues). SECSH key files
are not so different from PEM files, but still there are some
significant differencies and thus PEM file reading can not be used

If support for SECSH keys is added, I could convince our company to
upgrade to more recent version even if it would cause extra effort.

I have also been wondering whether libssh2 will ever catch the RFC
track? At least the early versions of libssh2 were based on internet
drafts and quite many of those drafts are now RFC's
259). As OpenSSH is the main target for compatbility I can understand
that there is real pressure but still it would be nice to be fully
standard compliant (at least in the roadmap if not anywhere else).



perl -e '$@=[[0,0112,0,0],[0,0101,0,0],
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