From: Ian Mullins <imullins@redhat.com>
To: u-boot@lists.denx.de
Cc: "Tom Rini" <trini@konsulko.com>,
"Heinrich Schuchardt" <xypron.glpk@gmx.de>,
"Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
"Ian Mullins" <imullins@redhat.com>,
"Enric Balletbo i Serra" <eballetbo@kernel.org>,
"Enric Balletbo Serra" <eballetb@redhat.com>,
"Bin Meng" <bmeng.cn@gmail.com>,
"Michal Simek" <michal.simek@amd.com>,
"Vincent Stehlé" <vincent.stehle@arm.com>,
"Simon Glass" <sjg@chromium.org>,
"Peter Robinson" <pbrobinson@gmail.com>,
"Quentin Schulz" <quentin.schulz@cherry.de>,
"Shantur Rathore" <i@shantur.com>,
"Aswin Murugan" <aswin.murugan@oss.qualcomm.com>,
"Sughosh Ganu" <sughosh.ganu@arm.com>,
"Masahisa Kojima" <kojima.masahisa@socionext.com>,
"Marek Vasut" <marek.vasut+renesas@mailbox.org>,
"Udit Kumar" <u-kumar1@ti.com>
Subject: [PATCH 0/2] efi: Implement EFI Security Architecture protocols
Date: Fri, 10 Jul 2026 14:23:07 +0100 [thread overview]
Message-ID: <20260710-efi_security_protocol-v1-0-a06cef90057b@redhat.com> (raw)
This series implements the EFI_SECURITY_ARCH_PROTOCOL and
EFI_SECURITY2_ARCH_PROTOCOL. The primary motivation is to support EFI
applications like systemd-stub in Unified Kernel Images (UKI) so they
can temporarily override authentication for embedded payloads.
Note: This work was originally authored by Enric Balletbo i Serra.
I am submitting it upstream on his behalf with additional testing.
---
Testing Performed
I have validated these patches across various secure boot scenarios on
both physical hardware and emulators to ensure the new overrides work
without regressing standard secure boot enforcement.
Hardware: Renesas R-Car S4 (EBBR UKI boot)
- [PASS] Unsigned image, Secure Boot disabled, without patch
(Boots)
- [PASS] Unsigned image, Secure Boot compiled (not enforcing),
without patch (Boots)
- [PASS] Signed image, Secure Boot enforcing, without patch
(Fails to boot as expected)
- [PASS] Signed image, Secure Boot enforcing, with patch
(Boots successfully)
- [PASS] Signed image (wrong keys), Secure Boot enforcing, with patch
(Fails to boot as expected)
Emulator: QEMU (qemu UKI boot)
- [PASS] Unsigned image, Secure Boot disabled, without patch
(Boots)
- [PASS] Unsigned image, Secure Boot enabled, without patch
(Boots)
- [PASS] Signed image, Secure Boot enabled, without patch
(Fails to boot as expected)
- [PASS] Signed image, Secure Boot enabled, with patch
(Boots successfully)
Signed-off-by: Ian Mullins <imullins@redhat.com>
---
Enric Balletbo i Serra (2):
efi_loader: implement EFI Security Architecture protocols
efi_selftest: add tests for security architecture protocols
include/efi_api.h | 30 +++
include/efi_loader.h | 15 +-
lib/efi_loader/Kconfig | 11 ++
lib/efi_loader/Makefile | 1 +
lib/efi_loader/efi_boottime.c | 3 +-
lib/efi_loader/efi_image_loader.c | 31 ++-
lib/efi_loader/efi_security.c | 99 ++++++++++
lib/efi_loader/efi_setup.c | 7 +
lib/efi_selftest/Makefile | 1 +
lib/efi_selftest/efi_selftest_security_arch.c | 110 +++++++++++
.../py/tests/test_efi_secboot/README.security_arch | 208 +++++++++++++++++++++
.../tests/test_efi_secboot/test_security_arch.py | 73 ++++++++
12 files changed, 580 insertions(+), 9 deletions(-)
---
base-commit: 913fedc816570c07bfc7f9c4046dc2a3a55e4099
change-id: 20260710-efi_security_protocol-6b9fb0e8da41
Best regards,
--
Ian Mullins <imullins@redhat.com>
next reply other threads:[~2026-07-10 18:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 13:23 Ian Mullins [this message]
2026-07-10 13:23 ` [PATCH 1/2] efi_loader: implement EFI Security Architecture protocols Ian Mullins
2026-07-27 11:07 ` Ilias Apalodimas
2026-07-10 13:23 ` [PATCH 2/2] efi_selftest: add tests for security architecture protocols Ian Mullins
2026-07-23 12:11 ` [PATCH 0/2] efi: Implement EFI Security Architecture protocols Mattijs Korpershoek
2026-07-23 18:50 ` Ilias Apalodimas
2026-07-27 12:34 ` Heinrich Schuchardt
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=20260710-efi_security_protocol-v1-0-a06cef90057b@redhat.com \
--to=imullins@redhat.com \
--cc=aswin.murugan@oss.qualcomm.com \
--cc=bmeng.cn@gmail.com \
--cc=eballetb@redhat.com \
--cc=eballetbo@kernel.org \
--cc=i@shantur.com \
--cc=ilias.apalodimas@linaro.org \
--cc=kojima.masahisa@socionext.com \
--cc=marek.vasut+renesas@mailbox.org \
--cc=michal.simek@amd.com \
--cc=pbrobinson@gmail.com \
--cc=quentin.schulz@cherry.de \
--cc=sjg@chromium.org \
--cc=sughosh.ganu@arm.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=u-kumar1@ti.com \
--cc=vincent.stehle@arm.com \
--cc=xypron.glpk@gmx.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