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 159801FF145 for ; Thu, 05 Feb 2026 13:12:20 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id CB03DE65F; Thu, 5 Feb 2026 13:12:51 +0100 (CET) Message-ID: <6a0cf7d8-ea1e-4bff-b1db-0303c9df7a4b@proxmox.com> Date: Thu, 5 Feb 2026 13:12:15 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [pve-devel] [PATCH-SERIES qemu-server/manager/docs v3 0/3] improve Microsoft+Windows UEFI CA 2023 enrollment From: Fiona Ebner To: pve-devel@lists.proxmox.com References: <20260121154453.285642-1-f.ebner@proxmox.com> Content-Language: en-US In-Reply-To: <20260121154453.285642-1-f.ebner@proxmox.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1770293458483 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.017 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 RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. 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: MKASXPIJ7YN3WZEUI7UKP3XYYICORXS6 X-Message-ID-Hash: MKASXPIJ7YN3WZEUI7UKP3XYYICORXS6 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 Reply-To: Proxmox VE development discussion List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Am 21.01.26 um 4:44 PM schrieb Fiona Ebner: > Changes in v3: > * drop already applied patches > * squash ui patches > * add additional newline in confirm dialog to better separate subject > from note > * move enrollment to Disk Actions menu > * also suggest and support enrollment for non-Windows guests (Linux > distro shims are also signed with the Microsoft KEK) > * add docs patch > > 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). Ping