[pve-devel] [PATCH docs v3 3/3] qm: bios/uefi: add secure boot certificate expiration section

[Fiona Ebner <f.ebner@proxmox.com>]

Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
---

New in v3.

 qm.adoc | 49 ++++++++++++++++++++++++++++++++++++++++++++++++-
 1 file changed, 48 insertions(+), 1 deletion(-)

diff --git a/qm.adoc b/qm.adoc
index 667fd56..197a247 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,52 @@ 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=2023w` 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=2023w` 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 <vmid>
+----
+
+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 <drive>
+----
+
+For example, `<drive>` 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].
+
 [[qm_tpm]]
 Trusted Platform Module (TPM)
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- 
2.47.3



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel