public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH-SERIES qemu-server/manager v2 0/9] improve Microsoft+Windows UEFI CA 2023 enrollment
Date: Tue, 13 Jan 2026 11:54:14 +0100	[thread overview]
Message-ID: <20260113105440.68336-1-f.ebner@proxmox.com> (raw)

Changes in v2:
* add patch to also enroll the Windows UEFI CA 2023
* improve readability of change_drive() function
* ui: add more context to confirmation dialog
* add patch introducing a '2023w' marker so that drives already
  enrolled with only the MS 2023 cert can still be detected as needing
  enrollment

Make it possible to enroll via the API and UI by setting the
ms-cert=2023w marker on the EFI disk.

The previous Microsoft UEFI CA 2011 will expire in June 2026, and the
previous Windows UEFI CA 2011 will expire in October 2026, so there
should be a way to update that can be automated and done while guests
are running.

pve-manager needs a dependency bump for qemu-server for the API call
to have the desired effect (or the marker will just get set without
actually enrolling).


qemu-server:

Fiona Ebner (6):
  qm enroll-efi-keys: do not remove EFI disk when config was modified
    during operation
  ovmf: enroll ms 2023 cert: pass along parsed drive
  config: apply pending: code style: avoid some line bloat
  config: apply pending: efi: enroll Microsoft UEFI CA 2023 when setting
    ms-cert=2023 option
  ovmf: also enroll the Windows UEFI CA 2023 key
  efi disk: distinguish between having only MS 2023 cert and also having
    Windows 2023 cert

 src/PVE/CLI/qm.pm           | 21 ++++++----------
 src/PVE/QemuServer.pm       | 22 ++++++++++-------
 src/PVE/QemuServer/Drive.pm |  6 +++--
 src/PVE/QemuServer/OVMF.pm  | 48 ++++++++++++++++++++++++++++---------
 4 files changed, 62 insertions(+), 35 deletions(-)


pve-manager:

Fiona Ebner (3):
  ui: qemu: hd efi: fix typo in warning
  ui: qemu: hardware: efi: allow enrolling Microsoft+Windows UEFI CA
    2023
  ui: qemu: hardware: efi: use 2023w value when enrolling certs

 www/manager6/qemu/HDEfi.js        |  2 +-
 www/manager6/qemu/HardwareView.js | 82 +++++++++++++++++++++++++++++++
 2 files changed, 83 insertions(+), 1 deletion(-)


Summary over all repositories:
  6 files changed, 145 insertions(+), 36 deletions(-)

-- 
Generated by git-murpp 0.5.0


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


             reply	other threads:[~2026-01-13 10:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-13 10:54 Fiona Ebner [this message]
2026-01-13 10:54 ` [pve-devel] [PATCH qemu-server v2 1/9] qm enroll-efi-keys: do not remove EFI disk when config was modified during operation Fiona Ebner
2026-01-13 10:54 ` [pve-devel] [PATCH qemu-server v2 2/9] ovmf: enroll ms 2023 cert: pass along parsed drive Fiona Ebner
2026-01-13 10:54 ` [pve-devel] [PATCH qemu-server v2 3/9] config: apply pending: code style: avoid some line bloat Fiona Ebner
2026-01-13 10:54 ` [pve-devel] [PATCH qemu-server v2 4/9] config: apply pending: efi: enroll Microsoft UEFI CA 2023 when setting ms-cert=2023 option Fiona Ebner
2026-01-13 10:54 ` [pve-devel] [PATCH qemu-server v2 5/9] ovmf: also enroll the Windows UEFI CA 2023 key Fiona Ebner
2026-01-13 10:54 ` [pve-devel] [PATCH qemu-server v2 6/9] efi disk: distinguish between having only MS 2023 cert and also having Windows 2023 cert Fiona Ebner
2026-01-13 10:54 ` [pve-devel] [PATCH manager v2 7/9] ui: qemu: hd efi: fix typo in warning Fiona Ebner
2026-01-13 10:54 ` [pve-devel] [PATCH manager v2 8/9] ui: qemu: hardware: efi: allow enrolling Microsoft+Windows UEFI CA 2023 Fiona Ebner
2026-01-13 10:54 ` [pve-devel] [PATCH manager v2 9/9] ui: qemu: hardware: efi: use 2023w value when enrolling certs Fiona Ebner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260113105440.68336-1-f.ebner@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal