From: Septatrix <24257556+Septatrix@users.noreply.github.com>
Date: Tue, 12 Dec 2023 17:21:56 +0000 (+0100)
Subject: docs: Mention OVMF files with MS certs enrolled
X-Git-Tag: v20~74
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=5edcc50578b3a7a895a3bdec09a2da9c2e8d311d;p=thirdparty%2Fmkosi.git

docs: Mention OVMF files with MS certs enrolled
---

diff --git a/mkosi/resources/mkosi.md b/mkosi/resources/mkosi.md
index 3da290e2f..e0018f489 100644
--- a/mkosi/resources/mkosi.md
+++ b/mkosi/resources/mkosi.md
@@ -1340,6 +1340,13 @@ boolean argument: either `1`, `yes`, or `true` to enable, or `0`, `no`,
   [virt-firmware](https://gitlab.com/kraxel/virt-firmware) project can
   be used to customize OVMF variable files.
 
+: Some distributions also provide variable files which already have
+  Microsoft's certificates for secure boot enrolled. For Fedora
+  and Debian these are `OVMF_VARS.secboot.fd` and `OVMF_VARS_4M.ms.fd`
+  under `/usr/share/OVMF` respectively. You can use `locate` and look
+  under `/usr/share/qemu/firmware` for hints on where to find these
+  files if your distribution ships them.
+
 `QemuKernel=`, `--qemu-kernel=`
 
 : Set the kernel image to use for qemu direct kernel boot. If not