From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 277DA1FF136 for ; Mon, 23 Feb 2026 16:26:03 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 2CFFA112DB; Mon, 23 Feb 2026 16:26:37 +0100 (CET) From: Fiona Ebner To: pve-devel@lists.proxmox.com Subject: [PATCH docs v4 6/6] qm: bios/uefi: add secure boot certificate expiration section Date: Mon, 23 Feb 2026 16:25:38 +0100 Message-ID: <20260223152556.197761-7-f.ebner@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260223152556.197761-1-f.ebner@proxmox.com> References: <20260223152556.197761-1-f.ebner@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1771860345608 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.012 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: ZBFLPYNTICAE2J7JVDC3AI2F3X4QCVST X-Message-ID-Hash: ZBFLPYNTICAE2J7JVDC3AI2F3X4QCVST X-MailFrom: f.ebner@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Signed-off-by: Fiona Ebner --- Changes in v4: * use 2023k instead of 2023w * mention that 2023w and 2023 may indicate partial enrollment qm.adoc | 52 +++++++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 51 insertions(+), 1 deletion(-) diff --git a/qm.adoc b/qm.adoc index 667fd56..8f55794 100644 --- a/qm.adoc +++ b/qm.adoc @@ -1121,7 +1121,8 @@ the GUI). *pre-enroll-keys* specifies if the efidisk should come pre-loaded with distribution-specific and Microsoft Standard Secure Boot keys. It also enables Secure Boot by default (though it can still be disabled in the OVMF menu within -the VM). +the VM). See also +xref:qm_secure_boot_ca_expiration[Secure Boot Certificate Expiration]. NOTE: If you want to start using Secure Boot in an existing VM (that still uses a '2m' efidisk), you need to recreate the efidisk. To do so, delete the old one @@ -1137,6 +1138,55 @@ When using OVMF with PXE boot, you have to add an xref:qm_virtio_rng[RNG device] to the VM. For security reasons, the OVMF firmware disables PXE boot for guests without a random number generator. +[[qm_secure_boot_ca_expiration]] +Secure Boot Certificate Expiration +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +The expiration date for the original set of Microsoft certificates from 2011, +which are used for secure boot for Windows and common Linux distributions, is +June 2026. New certificates were created in 2023 +footnote:[Microsoft support article about the issue +https://support.microsoft.com/en-us/topic/windows-secure-boot-certificate-expiration-and-ca-updates-7ff40d33-95dc-4c3c-8725-a9b95457578e]. + +When secure boot is used, only bootloaders signed with certificates present on +the EFI disk will be allowed by the firmware. In particular, when an EFI disk +has only the 2011 certificates, bootloaders signed with the 2023 certificates +will be rejected. The presence of the `ms-cert=2023k` marker in the VM +configuration for an EFI disk indicates that the new certificates are enrolled. + +If the `pve-edk2-firmware` package version is at least `4.2025.05-1`, newly +created EFI disks contain both the 2011 and 2023 certificates and will have the +`ms-cert=2023k` marker. For EFI disks created before that, select the EFI disk +in the 'Hardware' view in the UI and use 'Disk Action > Enroll Updated +Certificates'. Alternatively, the marker can be set via the +`/nodes/{node}/qemu/{vmid}/config` API endpoint or via the + +---- +qm enroll-efi-keys +---- + +CLI command. The latter works if the VM is shut down. + +For Windows with BitLocker, run the following command inside Powershell: + +---- +manage-bde -protectors -disable +---- + +For example, `` could be `C:`. This is required for each drive with +BitLocker before proceeding! Otherwise, you will be prompted for the BitLocker +recovery key on the next boot! + +For proceeding with updating secure boot within Windows and signing the +bootloader with the new 2023 certificate, see +footnote:[Microsoft support article regarding CVE-2023-24932 +https://support.microsoft.com/en-us/topic/enterprise-deployment-guidance-for-cve-2023-24932-88b8f034-20b7-4a45-80cb-c6049b0f9967] +footnote:[Related Windows security update which needs to be installed first +https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-24932]. + +NOTE: The markers `ms-cert=2023` and `ms-cert=2023w` may indicate partial +enrollment. You should apply the enrollment procedure for such EFI drives too. + [[qm_tpm]] Trusted Platform Module (TPM) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- 2.47.3