mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH 0/3] code-signing: add provider support
Date: Wed, 22 Apr 2026 16:58:38 +0200	[thread overview]
Message-ID: <20260422-code-signing-provider-v1-0-ce986114c54d@pengutronix.de> (raw)

openssl engines have been deprecated for a long time. Add provider
support to the ptxdist code signing infrastructure.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
Sascha Hauer (3):
      host-libp11: use correct path for ossl-modules
      Add host-pkcs11-provider
      code-signing: enable provider support

 platforms/code-signing.in               |  1 +
 rules/host-libp11.make                  |  1 +
 rules/host-pkcs11-provider.in           | 10 ++++++++++
 rules/host-pkcs11-provider.make         | 33 +++++++++++++++++++++++++++++++++
 rules/host-softhsm.in                   |  1 +
 rules/host-softhsm.make                 | 27 +++++++++++++++++++++++++++
 rules/pre/010-code-signing.make         |  2 +-
 rules/pre/020-code-signing-softhsm.make |  3 ++-
 8 files changed, 76 insertions(+), 2 deletions(-)
---
base-commit: 9e28c99dd6a5b30c578b75deb71bd82d41fda429
change-id: 20260422-code-signing-provider-394214622a4c

Best regards,
-- 
Sascha Hauer <s.hauer@pengutronix.de>




             reply	other threads:[~2026-04-22 14:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-22 14:58 Sascha Hauer [this message]
2026-04-22 14:58 ` [ptxdist] [PATCH 1/3] host-libp11: use correct path for ossl-modules Sascha Hauer
2026-04-22 14:58 ` [ptxdist] [PATCH 2/3] Add host-pkcs11-provider Sascha Hauer
2026-04-23  7:50   ` Sascha Hauer
2026-04-22 14:58 ` [ptxdist] [PATCH 3/3] code-signing: enable provider support Sascha Hauer

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=20260422-code-signing-provider-v1-0-ce986114c54d@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=ptxdist@pengutronix.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