[Buildroot] [PATCH 1/1] package/libssh: add support for mbedtls crypto backend

Arnout Vandecappelle arnout at mind.be
Mon Sep 23 13:31:20 UTC 2019

On 23/09/2019 12:22, Mircea Gliga wrote:
> Hi Thomas,
> Sorry for the misunderstanding, I re-read your question.
>> My point was: is it really useful to
>> provide an explicit choice vs. simply selecting a preferred crypto
>> provider automatically, with no explicit choice in Config.in.
> Yes it's useful if for some reason you have multiple backends already
> present: for example one package has a hard dependency on openSSL and I
> want mine to use libssh with mbedTLS. In this case you have to manually
> choose your crypto backend as the default is not suitable for your needs.

 Yes, but the real question then is: why would mbedTLS ever be more suitable for
your needs than openssl (when used as a backend for libssh)?

 I remember there was a patch doing something similar for another package at
some point, and there the explanation was that (IIRC) with gnutls you could use
a crypto token but with openssl you couldn't. So, if there is something like
that at play here as well, please explain it in the commit message.


More information about the buildroot mailing list