From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id EDC4B1FF135 for ; Thu, 02 Jul 2026 15:55:53 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id BC3DD213DC; Thu, 02 Jul 2026 15:55:53 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Maximiliano Sandoval Subject: applied: [PATCH docs v2 1/1] bootloaders: add secure boot shim example Date: Thu, 2 Jul 2026 15:55:11 +0200 Message-ID: <178300050983.3208500.9025729287746214170.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260702093215.84124-1-m.sandoval@proxmox.com> References: <20260702093215.84124-1-m.sandoval@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1783000513512 X-SPAM-LEVEL: Spam detection results: 0 DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) 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: EXAFCDGSX6ZP3M536JCPJ7SIDYX6PJ2U X-Message-ID-Hash: EXAFCDGSX6ZP3M536JCPJ7SIDYX6PJ2U X-MailFrom: t.lamprecht@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 List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Thu, 02 Jul 2026 11:31:58 +0200, Maximiliano Sandoval wrote: > On a system that was migrated from systemd-boot to grub2 with secure > boot, the entry grubx64.efi would be missing and the systemd-bootx64.efi > entry would be present. If the shimx64.efi entry is not mentioned, then > the docs would incorrectly imply that the system uses systemd-boot as a > bootloader. > > We add the shimx64.efi entry to the docs to fill this gap. > > [...] Applied, thanks! [1/1] bootloaders: add secure boot shim example commit: d4093b7ffb78385ae6f5e125e99bbf31c131e3a0