build_library: Update our temporary Secure Boot CA certificate#4140
Merged
Conversation
As a reminder, this is what we're using for official releases until we get a formally signed certificate from Microsoft. Signed-off-by: James Le Cuirot <jlecuirot@microsoft.com>
There was a problem hiding this comment.
Pull request overview
This PR updates the temporary Secure Boot development CA certificate used by build_library tooling to generate QEMU UEFI Secure Boot variable stores for official releases (until a Microsoft-signed cert is available).
Changes:
- Update the default
virt-fw-vars --add-dbextra DB certificate from the old shim cert to the new dev CA PEM. - Remove the old
flatcar-sb-dev-shim-2025.certfrom the repository. - Add the new
flatcar-sb-dev-ca.pemcertificate file.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| build_library/vm_image_util.sh | Switch default extra Secure Boot DB cert injection to flatcar-sb-dev-ca.pem. |
| build_library/flatcar-sb-dev-shim-2025.cert | Remove the superseded shim certificate. |
| build_library/flatcar-sb-dev-ca.pem | Add the updated temporary Secure Boot development CA certificate. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
tormath1
approved these changes
Jul 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As a reminder, this is what we're using for official releases until we get a formally signed certificate from Microsoft.
How to use
Short of doing a release, you can recreate flatcar_production_qemu_uefi_secure_efi_vars.qcow2 with virt-fw-vars and pass that to flatcar_production_qemu_uefi_secure.sh with
-W.Testing done
I've done the above. It successfully booted, and
mokutil --sb-stateshowed Secure Boot was enabled.changelog/directory (user-facing change, bug fix, security fix, update) -- N/A/bootand/usrsize, packages, list files for any missing binaries, kernel modules, config files, kernel modules, etc. -- N/A