crypto engine

[Will Cosgrove]

You can test if backend defines are set, like so:

#ifdef LIBSSH2_OPENSSL
	//enabled
#endif

#ifdef LIBSSH2_LIBGCRYPT
	//enabled
#endif


Will

> On Nov 19, 2021, at 7:41 AM, Bastien Durel via libssh2-devel <libssh2-devel at lists.haxx.se> wrote:
> 
> Hello,
> 
> Is there a way to say during runtime (or maybe at compile time) which
> crypto engine is backing libssh2 ?
> 
> The code I wrote uses libssh2_userauth_publickey_frommemory, which
> fails with LIBSSH2_ERROR_PUBLICKEY_UNVERIFIED / "Callback returned
> error" when the crypto engine is not OpenSSL.
> I'd like to know if I have to write key material to temporary files
> 
> Debian version of libssh2 is built against libgcrypt20 but arch's
> version is built against openssl, which confused me a lot :/
> 
> Thanks,
> 
> -- 
> Bastien Durel
> DATA
> Intégration des données de l'entreprise,
> Systèmes d'information décisionnels.
> 
> bastien.durel at data.fr
> tel : +33 (0) 1 57 19 59 28
> fax : +33 (0) 1 57 19 59 73
> 45 avenue Carnot, 94230 CACHAN France
> www.data.fr
> 
> -- 
> libssh2-devel mailing list
> libssh2-devel at lists.haxx.se
> https://lists.haxx.se/listinfo/libssh2-devel