public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Wojciech Dubowik <Wojciech.Dubowik@mt.com>
To: Franz Schnyder <fra.schnyder@gmail.com>
Cc: openembedded-core@lists.openembedded.org, u-boot@lists.denx.de,
	simon.glass@canonical.com,
	Francesco Dolcini <francesco@dolcini.it>
Subject: Re: - Host GnuTLS now needs pkcs11 support
Date: Wed, 8 Apr 2026 08:50:41 +0200	[thread overview]
Message-ID: <adX6wVUWvNrzYfuV@mt.com> (raw)
In-Reply-To: <f5ov7deig7xaovxmtx3nhewki6mudgebahghknhxodlfa3lrdh@ary63d3fodkz>

On Tue, Apr 07, 2026 at 06:15:13PM +0200, Franz Schnyder wrote:
Hello Franz,
> Hello Wojciech,
> 
> with commit 0c716a157be ("tools: mkeficapsule: Add support for pkcs11"),
> mkeficapsule now references to pkcs11 related symbols.
> 
> This breaks our OE builds because it causes link failures for 
> configurations that build mkeficapsule when the host gnutls is 
> built without pkcs11 support:
> ```
> undefined reference to `gnutls_pkcs11_obj_list_import_url4'
> undefined reference to `gnutls_x509_crt_import_pkcs11'
> undefined reference to `gnutls_pkcs11_init'
> undefined reference to `gnutls_pkcs11_add_provider'
> undefined reference to `gnutls_pkcs11_deinit'
> ```
> On the OE side, enabling support in gnutls via p11-kit fixes the failures.
> However, I wonder what the cleanest solution would be. Should this new 
> host requirement for pkcs11 be handled in the U-Boot OE recipe,  or is
> there a better way to approach this correctly?
> 
> Any ideas?
I could add disable compile flag in mkeficapsule if there are no objections. Sth
like this in pkcs11 places:

+#ifndef DISABLE_PKCS11
                ret = gnutls_privkey_import_pkcs11_url(pkey, ctx->key_file);
[...]
+#else
+               fprintf(stdout, "Pkcs11 support is disabled\n");
+               return -1;
+#endif

This way OE or possibly openwrt don't need to patch.

Regards,
Wojtek

> 
> Kind regards
> 
> Franz


       reply	other threads:[~2026-04-08  7:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f5ov7deig7xaovxmtx3nhewki6mudgebahghknhxodlfa3lrdh@ary63d3fodkz>
2026-04-08  6:50 ` Wojciech Dubowik [this message]
2026-04-08 14:16   ` EXTERNAL - Host GnuTLS now needs pkcs11 support Franz Schnyder
2026-04-08 16:14   ` Tom Rini

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=adX6wVUWvNrzYfuV@mt.com \
    --to=wojciech.dubowik@mt.com \
    --cc=fra.schnyder@gmail.com \
    --cc=francesco@dolcini.it \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=simon.glass@canonical.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