From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 960E71FF187 for ; Tue, 18 Nov 2025 14:32:53 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id A814614D7D; Tue, 18 Nov 2025 14:32:57 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Fiona Ebner Date: Tue, 18 Nov 2025 14:30:00 +0100 Message-ID: <176347259808.1206474.115598923390616956.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20251118123516.112546-1-f.ebner@proxmox.com> References: <20251118123516.112546-1-f.ebner@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1763472713422 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.023 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 Subject: Re: [pve-devel] [PATCH-SERIS qemu-server 0/4] vm start: ovmf: do not auto-enroll Microsoft UEFI CA 2023 X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" On Tue, 18 Nov 2025 13:34:38 +0100, Fiona Ebner wrote: > As reported in the community forum [0], enrolling the new certificate > will trigger BitLocker recovery. It doesn't seem to be possible to > detect whether BitLocker is used by looking at the EFI var store (no > telling difference in dumps with 'virt-fw-vars --output-json' before > and after). > > Stop auto-enrolling the new Microsoft UEFI 2023 certificate and > produce a warning, telling users about the 'qm enroll-efi-keys' > command and what steps to take when BitLocker is used to avoid > triggering recovery. Thomas found [1], which suggests using > 'manage-bde -protectors -disable' which will disable key protectors > for the next boot and this was also successfully tested. > > [...] Applied with two changes squashed in, thanks! For one I replaced the log_warn with print for now to avoid being to noisy already, we can "turn up the heat" for this early next year, e.g. for PVE 9.2. Then I also moved new command out of the API, keeping it purely to the qm CLI for now to avoid having to comit to this new API for the PVE 9 lifetime, especially as we got some other ideas to handle this in a recent off list talk. [1/4] ovmf: enroll ms 2023 cert: change QSD ID to allow calling outside of VM start commit: 4effab683fc9d0a4e85d9435d84fccff56e69101 [2/4] api/cli: add enroll-efi-keys endpoint commit: ee296e6eb10577ee90bfbb201beb5487bb81bda6 [3/4] ovmf: factor out helper for checking whether MS 2023 certificate should be enrolled commit: 16750f2a6023f1304e445beb2d9504d51c090bfc [4/4] vm start: ovmf: do not auto-enroll Microsoft UEFI CA 2023 commit: 6952b33bb976f3afe1369e7333e3aa3cc9dc2f1a _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel