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 A92B11FF17A for ; Tue, 11 Nov 2025 11:58:48 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id EBD7C694A; Tue, 11 Nov 2025 11:59:34 +0100 (CET) Message-ID: Date: Tue, 11 Nov 2025 11:59:00 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Beta To: Proxmox VE development discussion , Fiona Ebner References: <20251106154314.772317-1-f.ebner@proxmox.com> Content-Language: en-US From: Thomas Lamprecht In-Reply-To: <20251106154314.772317-1-f.ebner@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1762858717968 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.024 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 Subject: [pve-devel] applied: [PATCH-SERIES edk2-firmware 0/6] partially fix #6985: pre-enroll Microsoft UEFI CA 2023 keys 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" Am 06.11.25 um 16:43 schrieb Fiona Ebner: > This fixes the issue with the Microsoft UEFI CA 2011 expiring in June > 2026 for new EFI disks. What still needs to be done is giving users a > way for (or automatically) enrolling the new keys to existing EFI > disks. I will look at that part of the issue in the coming days. > > To update an existing EFI disk, it should be enough to do something > like: > virt-fw-vars --inplace vm-103-disk-0.raw --distro-keys ms-uefi > > AFAICS, virt-fw-vars can only deal with raw images, so we can use FUSE > exports of differently formatted EFI disks which requires [0]. > > [0]: https://lore.proxmox.com/pve-devel/20251020141335.124077-1-f.ebner@proxmox.com/ > > > pve-edk2-firmware: > > Fiona Ebner (6): > update edk2 to edk2-stable202505 tag and refresh patches > d/patches: pick up CVE fix from Debian tag debian/2025.05-1 > d/rules: pick up some improvements from Debian > Use virt-firmware to enroll default keys. > Initialize the Secure Boot dbx in *.ms.fd with the latest revocations > partially fix #6985: pre-enroll Microsoft UEFI CA 2023 keys > > debian/DBXUpdate-2025-02-24.arm64.bin | Bin 0 -> 4613 bytes > debian/DBXUpdate-2025-10-16.amd64.bin | Bin 0 -> 24053 bytes > debian/control | 1 + > debian/edk2-vars-generator.py | 140 ---- > ...nrollDefaultKeys-with-Microsoft-2023.patch | 613 ++++++++++++++++++ > ...tLib-Fix-split-lock-violation-from-M.patch | 10 +- > ...CpuDxeSmm-Safe-handling-of-IDT-regis.patch | 45 ++ > debian/patches/series | 2 + > debian/rules | 99 +-- > debian/source/include-binaries | 2 + > edk2 | 2 +- > 11 files changed, 721 insertions(+), 193 deletions(-) > create mode 100644 debian/DBXUpdate-2025-02-24.arm64.bin > create mode 100644 debian/DBXUpdate-2025-10-16.amd64.bin > delete mode 100755 debian/edk2-vars-generator.py > create mode 100644 debian/patches/OvmfPkg-Expand-EnrollDefaultKeys-with-Microsoft-2023.patch > create mode 100644 debian/patches/UefiCpuPkg-PiSmmCpuDxeSmm-Safe-handling-of-IDT-regis.patch > > > Summary over all repositories: > 11 files changed, 721 insertions(+), 193 deletions(-) > applied series (pulled from your staff repo), thanks! _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel