summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorigo95862 <igo95862@yandex.ru>2023-01-03 10:18:58 +0300
committerLennart Poettering <lennart@poettering.net>2023-01-03 10:16:40 +0100
commit8d41101a4afc522e8e1232e3397811f5e971099e (patch)
tree72b7d302d3af59b2326f6e075b7afe87003b964d
parent4f06325ce97a072be84130c6ca8d29c52dcf9d0d (diff)
downloadsystemd-8d41101a4afc522e8e1232e3397811f5e971099e.tar.gz
man: Fix systemd-boot man page wrong secure keys location
The keys should be placed at `/loader/keys/` not `/keys/`. See `src/boot/efi/boot.c` file and function `secure_boot_discover_keys`.
-rw-r--r--man/systemd-boot.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/man/systemd-boot.xml b/man/systemd-boot.xml
index 6d99520036..442cf4179e 100644
--- a/man/systemd-boot.xml
+++ b/man/systemd-boot.xml
@@ -321,7 +321,7 @@
similar, to extend the native firmware support.</para>
<para>Enrollment of Secure Boot variables can be performed manually or automatically if files are available
- under <filename>/keys/<replaceable>NAME</replaceable>/{db,KEK,PK}.auth</filename>, <replaceable>NAME</replaceable>
+ under <filename>/loader/keys/<replaceable>NAME</replaceable>/{db,KEK,PK}.auth</filename>, <replaceable>NAME</replaceable>
being the display name for the set of variables in the menu. If one of the sets is named <filename>auto</filename>
then it might be enrolled automatically depending on whether <literal>secure-boot-enroll</literal> is set
to force or not.</para>