Skip to content

Add UEFI Secure Boot 2023 certificate transition guide#809

Merged
andrewlukoshko merged 1 commit into
masterfrom
secure-boot-2023-certificates
Jun 10, 2026
Merged

Add UEFI Secure Boot 2023 certificate transition guide#809
andrewlukoshko merged 1 commit into
masterfrom
secure-boot-2023-certificates

Conversation

@andrewlukoshko

@andrewlukoshko andrewlukoshko commented Jun 10, 2026

Copy link
Copy Markdown
Member

What

Adds a new Documentation page explaining the Microsoft 2011 → 2023 UEFI Secure Boot certificate transition (the 2011 CAs expire in June 2026), adds it to the Documentation navbar menu (between NVIDIA Drivers and FAQ), and references the dual-signed shim 16.1 at the top of the 9.8 and 10.2 release notes changelogs with a link to the new page.

Page URL after deploy: /documentation/secure-boot-2023-certificates.html

Contents

  • What expires in June 2026 and why existing systems keep booting
  • Current AlmaLinux shim signing status (verified against the actual binaries in our repos):
    • AlmaLinux 9/10 x86_64: dual-signed with 2011 + 2023 CAs — no action required
    • AlmaLinux 9/10 aarch64: 2023-only (same as RHEL)
    • AlmaLinux 8: 2011-only, update planned following RHEL 8 (June 2026)
  • How to check enrolled certificates with mokutil
  • Recommended update path via fwupd (2.0.19 in AlmaLinux 9/10 BaseOS), following RHEL guidance
  • Manual fallback using efivar (with attribute value in decimal — efivar 37/38 in EL8/EL9 don't parse hex)
  • VM guidance: KVM/libvirt (edk2-ovmf), VMware vSphere, Azure Trusted Launch, Google Cloud Shielded VM, AWS EC2
  • Caveats: TPM PCR 7 / LUKS auto-unlock resealing, HP/Fujitsu db-update blocks, why not to revoke the 2011 CA

Release notes

Both release-notes/9.8.md and release-notes/10.2.md get a lead paragraph in the Changelog section:

Shim 16.1 bootloader binaries for x86_64 are now dual-signed with both the Microsoft 2011 and 2023 UEFI Secure Boot certificates, see UEFI Secure Boot: Microsoft 2023 Certificate Transition for details.

References

Tested locally with vuepress dev: page renders, tables and code blocks OK, navbar entry shows in the intended position, release-notes paragraphs render with working links.

@jonathanspw

Copy link
Copy Markdown
Member

The forced line breaks in this are unnecessary and should be removed.

@andrewlukoshko andrewlukoshko force-pushed the secure-boot-2023-certificates branch from a213598 to b18bf30 Compare June 10, 2026 14:22
@andrewlukoshko

Copy link
Copy Markdown
Member Author

@jonathanspw updated PR

@bennyvasquez bennyvasquez left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. As a note, we should probably add a call out that points to it in the relevant releases on /release-notes/ just so it's even more discoverable.

Documents the Microsoft 2011 -> 2023 Secure Boot CA transition:
current AlmaLinux shim signing status, verification steps, the
recommended fwupd update path, manual efivar enrollment, and
guidance for KVM, VMware, Azure, GCP and AWS virtual machines.
Adds the page to the Documentation navbar menu and references the
dual-signed shim 16.1 in the 9.8 and 10.2 release notes changelogs.
@andrewlukoshko andrewlukoshko force-pushed the secure-boot-2023-certificates branch from b18bf30 to 3708099 Compare June 10, 2026 20:23
@andrewlukoshko andrewlukoshko merged commit 3761228 into master Jun 10, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants