Subject: Re: [libssh2] Libgcrypt port update

Re: [libssh2] Libgcrypt port update

From: Mononen Jussi <>
Date: Fri, 19 Jan 2007 10:25:22 +0200

>> Since RFC 4716 only describes the file format for public keys, would
>> another (and perhaps better) solution for you not be to actually only
>> use the private key? It contains the public key, after all, and as
>> far as I know there is only one widely used format for the public key
>> files. Then we avoid all the hassles related to the public key file
>> formats.

Yes it suits me, at the moment all my attempts originate from the
customer trouble I am facing.

>> One argument may be that you may want to keep those two things apart,
>> but to be able to do anything useful, libssh2 will need your private
>> key anyway. So I don't think it matters.

I agree, you only *need* the private key.


$[=1;@x=qw(A S D F G H J K L P);$"=q{};print @x[7,1,10,6];
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-19