On Fri, 19 Jan 2007, CVS commit messages for libssh2 wrote:
> Update of /cvsroot/libssh2/libssh2/src
> In directory sc8-pr-cvs6.sourceforge.net:/tmp/cvs-serv2702
>
> Modified Files:
> openssl.c
> Log Message:
> fix warning for memcpy()
Now isn't it annoying how these messages don't tell WHO
>> 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.
>> I still don't understand why you get errors from the SERVER though.
>> The public key that is sent over the wire should be in a well-defined
>> format, and that shouldn't be related to the disk format, if I
>> understand correctly. I'd assume that if you don't have a public key
>> in OpenSSH f
"Mononen Jussi" <[EMAIL PROTECTED]> writes:
>>> > I thought this was only about the disk-format, does it
>>> affect the wire
>>> > format also? I'd assume that the protocol clearly specified the
>>> > format of public keys on the wire.
>>> >
>>> The format of the blob which is sent over the wir
Sara Golemon <[EMAIL PROTECTED]> writes:
>> I have no idea how to test the server mode of libssh2 though. Is that
>> even supported? I see there are some RSA signing stuff going on, and
>> I'd assume that is for the server side, but right now I'm to deep into
>> details to remember how things
