From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/openvpn: add option to use mbed TLS instead of OpenSSL
Date: Fri, 15 May 2020 23:18:28 +0200 [thread overview]
Message-ID: <20200515231828.1657342a@windsurf.home> (raw)
In-Reply-To: <CACm0Nn0WyTPDnSyA+7bj10GddAstx0YkyUAuERcRSLSf0CyzRA@mail.gmail.com>
Hello,
On Sat, 16 May 2020 00:03:10 +0300
Ed Spiridonov <edo.rus@gmail.com> wrote:
> > The idea of using select BR2_PACKAGE_OPENSSL if !BR2_PACKAGE_MBEDTLS
> > was to keep the current behavior, i.e be backward compatible.
>
> Does it make sense?
> If OpenSSL is selected, it will be used as a crypto backend. So any
> build based on an existing .config remains the same.
What you say will work if:
(1) Your .mk file tests BR2_PACKAGE_OPENSSL and uses openssl if set,
before using mbedtls
(2) Users are using full .config and not defconfig files. Indeed, a
defconfig file today that has BR2_PACKAGE_OPENVPN=y will not have
BR2_PACKAGE_OPENSSL=y, because this is implied by
BR2_PACKAGE_OPENVPN=y. So such users would transition from using
OpenSSL as the crypto backend for openvpn to mbedtls.
I don't have a very strong feeling on this. I agree that on the other
hand, it's good to use a smaller crypto library by default if possible.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-05-15 21:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 22:31 [Buildroot] [PATCH] package/openvpn: add option to use mbed TLS instead of OpenSSL Ed Spiridonov
2020-05-15 17:30 ` Ed Spiridonov
2020-05-15 19:17 ` Heiko Thiery
2020-07-26 12:01 ` Ed Spiridonov
2020-05-15 20:10 ` Thomas Petazzoni
2020-05-15 20:39 ` Ed Spiridonov
2020-05-15 20:47 ` Thomas Petazzoni
[not found] ` <CACm0Nn0WyTPDnSyA+7bj10GddAstx0YkyUAuERcRSLSf0CyzRA@mail.gmail.com>
2020-05-15 21:18 ` Thomas Petazzoni [this message]
2020-05-18 1:45 ` Ed Spiridonov
2020-05-18 5:15 ` Thomas Petazzoni
2020-05-23 18:38 ` Ed Spiridonov
2020-07-10 18:39 ` Ed Spiridonov
2020-10-10 6:43 ` Ed Spiridonov
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=20200515231828.1657342a@windsurf.home \
--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