You're right; I forgot to deal with GnuTLS. This is because I always use OpenSSL...
However, I'm not sure it's a good idea to implement functionality for one cryptographic library and not for another because it's then hard for a client user to know whether he can rely or not on a particular feature. BTW, why would it be so difficult to implement for GnuTLS? JLC -----Message d'origine----- De : Mikhail Gusarov [mailto:dotted...@dottedmag.net] Envoyé : vendredi 27 mars 2009 12:25 À : libssh2 development Objet : Re: RE : For the interested ones : libssh2_userauth_publickey_fromfileandlibssh2_userauth_hostbased_fromfile with no need of thepublickey file Twas brillig at 12:15:51 27.03.2009 UTC+01 when jean-louis.char...@oikialog.com did gyre and gimble: JC> + p_bytes = BN_num_bytes(dsa->p) + 1; JC> + q_bytes = BN_num_bytes(dsa->q) + 1; JC> + g_bytes = BN_num_bytes(dsa->g) + 1; JC> + k_bytes = BN_num_bytes(dsa->pub_key) + 1; Seems that the patch works only with OpenSSL. Can you make it compiling with GnuTLS too? IIRC there is no way to easily do the same, so it can just "return -1" in this case. -- ------------------------------------------------------------------------------ _______________________________________________ libssh2-devel mailing list libssh2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libssh2-devel
