From: Eddie Kovsky <ekovsky@redhat.com>
To: Tom Rini <trini@konsulko.com>, Tobias Olausson <tobias@eub.se>,
Paul HENRYS <paul.henrys_ext@softathome.com>,
Simon Glass <sjg@chromium.org>, Jan Stancek <jstancek@redhat.com>,
Enric Balletbo i Serra <eballetb@redhat.com>,
a.fatoum@pengutronix.de, mark.kettenis@xs4all.nl,
Mattijs Korpershoek <mkorpershoek@kernel.org>,
Johannes Schneider <johannes.schneider@leica-geosystems.com>
Cc: u-boot@lists.u-boot-project.org,
Quentin Schulz <quentin.schulz@cherry.de>,
Bastian <bst@pengutronix.de>, Rasmus Villemoes <ravi@prevas.dk>,
Jaipaul Cheernam <jaipaul.cheernam@est.tech>
Subject: [PATCH v5 2/3] Add pkcs11-provider package to build dependencies
Date: Thu, 29 Oct 2026 14:13:42 -0600 [thread overview]
Message-ID: <20261029201348.730274-3-ekovsky@redhat.com> (raw)
In-Reply-To: <20261029201348.730274-1-ekovsky@redhat.com>
This package is needed to use PKCS11 with OpenSSL >= 3.0.
Signed-off-by: Eddie Kovsky <ekovsky@redhat.com>
---
doc/build/gcc.rst | 4 ++--
tools/docker/Dockerfile | 1 +
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/doc/build/gcc.rst b/doc/build/gcc.rst
index 1fef718ceecb..29a6a632e7e3 100644
--- a/doc/build/gcc.rst
+++ b/doc/build/gcc.rst
@@ -25,8 +25,8 @@ Depending on the build targets further packages maybe needed
sudo apt-get install bc bison build-essential coccinelle \
device-tree-compiler dfu-util efitools flex gdisk graphviz imagemagick \
- libgnutls28-dev libguestfs-tools libncurses-dev \
- libpython3-dev libsdl2-dev libssl-dev lz4 lzma lzma-alone openssl \
+ libgnutls28-dev libguestfs-tools libncurses-dev libpython3-dev \
+ libsdl2-dev libssl-dev lz4 lzma lzma-alone openssl pkcs11-provider \
pkg-config python3 python3-asteval python3-coverage python3-filelock \
python3-pkg-resources python3-pycryptodome python3-pyelftools \
python3-pytest python3-pytest-xdist python3-sphinxcontrib.apidoc \
diff --git a/tools/docker/Dockerfile b/tools/docker/Dockerfile
index 187320c26d59..109d6503d8cd 100644
--- a/tools/docker/Dockerfile
+++ b/tools/docker/Dockerfile
@@ -122,6 +122,7 @@ RUN --mount=type=cache,target=/var/cache/apt,sharing=locked \
openssl \
picocom \
parted \
+ pkcs11-provider \
pkg-config \
python-is-python3 \
python3 \
--
2.56.0
next prev parent reply other threads:[~2026-10-29 20:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 20:13 [PATCH v5 0/3] Add support for OpenSSL Provider API Eddie Kovsky
2026-10-29 20:13 ` [PATCH v5 1/3] " Eddie Kovsky
2026-10-31 14:11 ` Simon Glass
2026-10-29 20:13 ` Eddie Kovsky [this message]
2026-10-31 14:12 ` [PATCH v5 2/3] Add pkcs11-provider package to build dependencies Simon Glass
2026-10-29 20:13 ` [PATCH v5 3/3] rsa: load a pkcs11 token key through OSSL_STORE in the provider path Eddie Kovsky
2026-10-31 14:12 ` Simon Glass
2026-10-30 9:57 ` [PATCH v5 0/3] Add support for OpenSSL Provider API Quentin Schulz
2026-10-31 14:11 ` Simon Glass
2026-10-31 14:17 ` 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=20261029201348.730274-3-ekovsky@redhat.com \
--to=ekovsky@redhat.com \
--cc=a.fatoum@pengutronix.de \
--cc=bst@pengutronix.de \
--cc=eballetb@redhat.com \
--cc=jaipaul.cheernam@est.tech \
--cc=johannes.schneider@leica-geosystems.com \
--cc=jstancek@redhat.com \
--cc=mark.kettenis@xs4all.nl \
--cc=mkorpershoek@kernel.org \
--cc=paul.henrys_ext@softathome.com \
--cc=quentin.schulz@cherry.de \
--cc=ravi@prevas.dk \
--cc=sjg@chromium.org \
--cc=tobias@eub.se \
--cc=trini@konsulko.com \
--cc=u-boot@lists.u-boot-project.org \
/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