public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wojciech Dubowik <Wojciech.Dubowik@mt.com>
To: Simon Glass <sjg@chromium.org>
Cc: "u-boot@lists.denx.de" <u-boot@lists.denx.de>, trini@konsulko.com
Subject: Re: EXTERNAL - [PATCH 2/2] binman: Accept pkcs11 URI tokens for capsule updates
Date: Mon, 5 Jan 2026 09:48:39 +0100	[thread overview]
Message-ID: <aVt65_RL1KF2myTM@mt.com> (raw)
In-Reply-To: <CAFLszTjfwkAdc9LHvq29Y=hFtZcoqJdh64LPrBP0AJcr0VMAgw@mail.gmail.com>

On Sat, Dec 27, 2025 at 07:52:36AM -0700, Simon Glass wrote:
> Hi Wojciech,
> 
> On Tue, 16 Dec 2025 at 08:09, Wojciech Dubowik <Wojciech.Dubowik@mt.com> wrote:
> >
> > With pkcs11 support in mkeficapsule we can now accept URI
> > tokens and not only files.
> >
> > Signed-off-by: Wojciech Dubowik <Wojciech.Dubowik@mt.com>
> > ---
> >  tools/binman/etype/efi_capsule.py | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/tools/binman/etype/efi_capsule.py b/tools/binman/etype/efi_capsule.py
> > index 9f06cc88e6e5..8ab022915d9d 100644
> > --- a/tools/binman/etype/efi_capsule.py
> > +++ b/tools/binman/etype/efi_capsule.py
> > @@ -125,9 +125,9 @@ class Entry_efi_capsule(Entry_section):
> >          private_key = ''
> >          public_key_cert = ''
> >          if self.auth:
> > -            if not os.path.isabs(self.private_key):
> > +            if not os.path.isabs(self.private_key) and not 'pkcs11:' in self.private_key:
> >                  private_key =  tools.get_input_filename(self.private_key)
> > -            if not os.path.isabs(self.public_key_cert):
> > +            if not os.path.isabs(self.public_key_cert) and not 'pkcs11:' in self.public_key_cert:
> >                  public_key_cert = tools.get_input_filename(self.public_key_cert)
> >          data, payload, uniq = self.collect_contents_to_file(
> >              self._entries.values(), 'capsule_in')
> > --
> > 2.47.3
> >
> 
> Does this have a test case?

Not yet. I have seen that pkcs11 engine and softhsm test framework have been recently merged into
next so I will try to make a testcase for it.

Regards,
Wojtek

> 
> Regards,
> Simon

  reply	other threads:[~2026-01-05  8:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-16 15:08 [PATCH 0/2] UEFI Capsule - PKCS11 Support Wojciech Dubowik
2025-12-16 15:08 ` [PATCH 1/2] tools: mkeficapsule: Add support for pkcs11 Wojciech Dubowik
2025-12-16 15:08 ` [PATCH 2/2] binman: Accept pkcs11 URI tokens for capsule updates Wojciech Dubowik
2025-12-27 14:52   ` Simon Glass
2026-01-05  8:48     ` Wojciech Dubowik [this message]
2026-01-05 23:30       ` EXTERNAL - " Simon Glass

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=aVt65_RL1KF2myTM@mt.com \
    --to=wojciech.dubowik@mt.com \
    --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