From: David Lechner <dlechner@baylibre.com>
To: Wojciech Dubowik <Wojciech.Dubowik@mt.com>, u-boot@lists.denx.de
Cc: Simon Glass <sjg@chromium.org>,
Franz Schnyder <fra.schnyder@gmail.com>,
trini@konsulko.com,
"openembedded-core @ lists . openembedded . org"
<openembedded-core@lists.openembedded.org>,
Francesco Dolcini <francesco@dolcini.it>
Subject: Re: [PATCH v2] tools: mkeficapsule: Add disable pkcs11 menu option
Date: Mon, 20 Apr 2026 17:58:45 -0500 [thread overview]
Message-ID: <ec9b6639-00a0-4fc4-aee4-f57f9cb26a5b@baylibre.com> (raw)
In-Reply-To: <61daa047-74f0-4a76-a61f-de54ca4b716e@baylibre.com>
On 4/20/26 5:15 PM, David Lechner wrote:
> On 4/20/26 3:38 AM, Wojciech Dubowik wrote:
>> Some distros are using gnutls library without pkcs11 support
>> and linking of mkeficapsule will fail. Add disable pkcs11
>> option with default set to no so distros can control this
>> feature with config option.
>>
>> Suggested-by: Tom Rini <trini@konsulko.com>
>> Cc: Franz Schnyder <fra.schnyder@gmail.com>
>> Signed-off-by: Wojciech Dubowik <Wojciech.Dubowik@mt.com>
>> ---
>> Changes in v2:
>> - make use of stderr more consistent
>> - add missing ifndef around pkcs11 deinit functions
>> ---
>> tools/Kconfig | 8 ++++++++
>> tools/Makefile | 3 +++
>> tools/mkeficapsule.c | 17 ++++++++++++++++-
>> 3 files changed, 27 insertions(+), 1 deletion(-)
>>
>> diff --git a/tools/Kconfig b/tools/Kconfig
>> index ef33295b8ecd..ccc878595d3b 100644
>> --- a/tools/Kconfig
>> +++ b/tools/Kconfig
>> @@ -114,6 +114,14 @@ config TOOLS_MKEFICAPSULE
>> optionally sign that file. If you want to enable UEFI capsule
>> update feature on your target, you certainly need this.
>>
>> +config MKEFICAPSULE_DISABLE_PKCS11
>
> Options that disable something instead of enabling it are confusing.
> Can we make this MKEFICAPSULE_PKCS11 instead and invert the logic?
>
>> + bool "Disable pkcs11 support"
>> + depends on TOOLS_MKEFICAPSULE
>> + default n
>
> I think it would be more convenient if we did not require PKS11 by
> default. Otherwise, everyone using Open Embedded that doesn't have
> the "p11-kit" PACKAGECONFIG option set for GnuTLS set (which is the
> default) is going to get a build failure and have to research this
> and find the option and modify their config to fix the build.
>
> It seems like it would be better to make people who actually need
> PKCS11 possibly get an error by default instead and enable the
> option. This is pure speculation on my part, but it seems like
> this would be the smaller group.
>
Or maybe we could avoid the config option altogether and do something
with `pkg-config --libs gnutls --print-requires-private` at build time
to detect if `p11-kit-1` is used by gnutls or not?
next prev parent reply other threads:[~2026-04-20 22:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 8:38 [PATCH v2] tools: mkeficapsule: Add disable pkcs11 menu option Wojciech Dubowik
2026-04-20 10:16 ` Quentin Schulz
2026-04-21 8:30 ` Wojciech Dubowik
2026-04-21 9:52 ` Quentin Schulz
2026-04-20 22:15 ` David Lechner
2026-04-20 22:58 ` David Lechner [this message]
2026-04-21 8:34 ` Wojciech Dubowik
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=ec9b6639-00a0-4fc4-aee4-f57f9cb26a5b@baylibre.com \
--to=dlechner@baylibre.com \
--cc=Wojciech.Dubowik@mt.com \
--cc=fra.schnyder@gmail.com \
--cc=francesco@dolcini.it \
--cc=openembedded-core@lists.openembedded.org \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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