From 6175b6cb894c3408403b00f68eda28be4011026b Mon Sep 17 00:00:00 2001 From: Umut Tezduyar Lindskog Date: Wed, 9 Sep 2026 10:19:04 +0200 Subject: [PATCH] Align UEFI terminology MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Also fix below: “authenticode” → “Authenticode” “implementend” → “implemented” “next stage” → “next-stage” when used adjectivally. --- src/boot/UEFI_SECURITY.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/boot/UEFI_SECURITY.md b/src/boot/UEFI_SECURITY.md index 78e9c4e16c..7489ebb201 100644 --- a/src/boot/UEFI_SECURITY.md +++ b/src/boot/UEFI_SECURITY.md @@ -47,10 +47,10 @@ defined in the [Boot Loader Interface](https://systemd.io/BOOT_LOADER_INTERFACE/ ## Dependencies Neither of these components implements cryptographic primitives, cryptographic checks, or drivers. File -access to the ESP is implemented solely via the appropriate UEFI file protocols. Verification of next stage -payloads is implementend solely via the appropriate UEFI image load protocols, which means `authenticode` -signature checks are again done by the firmware or `Shim`. As a consequence, no external security-critical -libraries (such as OpenSSL or gnu-efi) are linked, embedded, or used. +access to the ESP is implemented solely via the UEFI Simple File System Protocol and UEFI File Protocol. +Verification of next-stage payloads is implemented solely via the UEFI Image Services, which means +`Authenticode` signature checks are again done by the firmware or `Shim`. As a consequence, no external +security-critical libraries (such as OpenSSL or gnu-efi) are linked, embedded, or used. ## Additional Resources BLS Type #1 entries allow the user to load two types of additional resources that can affect the system