Subject: Re: [libssh2] Libgcrypt port update

Re: [libssh2] Libgcrypt port update

From: Simon Josefsson <>
Date: Thu, 18 Jan 2007 14:31:52 +0100

"Mononen Jussi" <> writes:

>>> Sorry for being lazy, but could you point me towards the
>>> document that defines the SECSH key formats?
> No problem,

Ah. That format seems simpler to decode than PEM files, as far as I
can tell. No ASN.1. OpenSSH's ssh-keygen seem to be able to convert
to and from that format, but it is not clear to me whether OpenSSH can
use such files automatically?

I'm not sure, but I suppose curl want to be able to use the same keys
that OpenSSH uses, right Daniel? Perhaps a conversion step between
the formats could be acceptable, but most likely not.

If OpenSSH cannot easily use SECSH keys directly, I guess I'm stuck
implementing PEM file reading anyway -- however, I suspect
implementing SECSH keys as a first step will be easier. That would
allow me to finish the libgcrypt port, but with the restriction that
SECSH keys has to be used. That is a good first step.

Do you have code to read SECSH keys that you are willing to share?
That would help me to finish the libgcrypt port until Sara finds the
PEM file reading code.

I also note that the RFC is only informational.

> Can't tell the exact list, but the key format is one. There propably is
> not much that is not standard conforming, more likely the standard is
> more versatile and capable than the current libssh2 implementation. This
> is something that needs quite much studying since the whole SECSH
> document set is large. So my question transforms into "Who will check
> how conformant libssh2 actually is?".

If nobody steps forward, one approach is to wait for bug reports from


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