From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libssh: add support for mbedtls crypto backend
Date: Wed, 18 Sep 2019 17:48:59 +0200 [thread overview]
Message-ID: <20190918174859.1627727d@windsurf> (raw)
In-Reply-To: <20190918110609.7172-1-gliga.mircea@gmail.com>
Hello Mircea,
Thanks for this contribution!
On Wed, 18 Sep 2019 14:06:09 +0300
Mircea Gliga <gliga.mircea@gmail.com> wrote:
> +choice
> + prompt "Crypto Backend"
> + default BR2_PACKAGE_LIBSSH_LIBGCRYPT if BR2_PACKAGE_LIBGCRYPT
> + default BR2_PACKAGE_LIBSSH_OPENSSL if BR2_PACKAGE_OPENSSL
> + default BR2_PACKAGE_LIBSSH_MBEDTLS if BR2_PACKAGE_MBEDTLS
> + help
> + Select crypto library to be used in libssh.
> +
> +config BR2_PACKAGE_LIBSSH_MBEDTLS
> + bool "mbedtls"
> + depends on BR2_PACKAGE_MBEDTLS
> +
> +config BR2_PACKAGE_LIBSSH_LIBGCRYPT
> + bool "gcrypt"
> + depends on BR2_PACKAGE_LIBGCRYPT
> +
> +config BR2_PACKAGE_LIBSSH_OPENSSL
> + bool "openssl"
> + depends on BR2_PACKAGE_OPENSSL
> +
> +endchoice
> +endif
I am wondering if we really need an explicit choice option here. Can't
we just use one of the three crypto libraries, depending on which one
is available ? Is there a good benefit in being able to explicitly
select which crypto backend to use ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-09-18 15:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 11:06 [Buildroot] [PATCH 1/1] package/libssh: add support for mbedtls crypto backend Mircea Gliga
2019-09-18 15:48 ` Thomas Petazzoni [this message]
2019-09-23 6:11 ` Mircea Gliga
2019-09-23 7:22 ` Thomas Petazzoni
2019-09-23 10:22 ` Mircea Gliga
2019-09-23 13:31 ` Arnout Vandecappelle
2019-09-23 14:20 ` Mircea Gliga
2019-09-23 15:19 ` Arnout Vandecappelle
2019-09-24 13:26 ` [Buildroot] [PATCH v2] " Mircea Gliga
2019-10-02 5:16 ` Mircea Gliga
2020-02-02 19:36 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190918174859.1627727d@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox