From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4, 1/1] package/uacme: don't allow mbedtls with ualpn
Date: Sun, 26 Apr 2020 21:21:30 +0200 [thread overview]
Message-ID: <20200426192130.GD28666@scaer> (raw)
In-Reply-To: <20200426141309.61837b4f@windsurf.home>
Thomas, All,
On 2020-04-26 14:13 +0200, Thomas Petazzoni spake thusly:
> On Sun, 26 Apr 2020 13:36:39 +0200
> "Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
>
> > > +choice
> > > + prompt "Crypto Backend"
> > > + help
> > > + Select crypto library to be used in uacme.
> > > +
> > > +config BR2_PACKAGE_UACME_GNUTLS
> > > + bool "gnutls"
> > > + depends on BR2_PACKAGE_GNUTLS
> > > +
> > > +config BR2_PACKAGE_UACME_MBEDTLS
> > > + bool "mbedtls"
> > > + depends on BR2_PACKAGE_MBEDTLS
> > > + depends on !BR2_PACKAGE_UACME_UALPN
> > > +
> > > +comment "mbedtls crypto backend unavailable with ualpn"
> > > + depends on BR2_PACKAGE_MBEDTLS
> > > + depends on BR2_PACKAGE_UACME_UALPN
> > > +
> > > +config BR2_PACKAGE_UACME_OPENSSL
> > > + bool "openssl"
> > > + depends on BR2_PACKAGE_OPENSSL
> > > +
> > > +endchoice
> > Sorry, but this is still not correct: enable mbedtls, then enable uacme
> > and ualpn: there is no crypto backend selectable in the choice...
> Do we need a choice in the first place ?
We already have a few packages (libcurl, libssh, libssh2) that have a
choice for the crypto backend, so why not for uacme?
Yes, the above are all libraries, but that is not much different for an
application I believe.
Regards,
Yann E. MORIN.
> Thomas
> --
> Thomas Petazzoni, CTO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2020-04-26 19:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 11:05 [Buildroot] [PATCH v4, 1/1] package/uacme: don't allow mbedtls with ualpn Fabrice Fontaine
2020-04-26 11:36 ` Yann E. MORIN
2020-04-26 12:13 ` Thomas Petazzoni
2020-04-26 12:30 ` Fabrice Fontaine
2020-04-26 16:07 ` Nicola Di Lieto
2020-04-26 19:38 ` Yann E. MORIN
2020-04-26 19:21 ` Yann E. MORIN [this message]
2020-04-27 19:31 ` Thomas Petazzoni
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=20200426192130.GD28666@scaer \
--to=yann.morin.1998@free.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.