From: "'Cetin, Gokhan' via isar-users" <isar-users@googlegroups.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "quirin.gylstorff@siemens.com" <quirin.gylstorff@siemens.com>,
"MOESSBAUER, Felix" <felix.moessbauer@siemens.com>
Subject: [PATCH] doc/user_manual: mention EFI variable access and platform keyring for module signing
Date: Mon, 20 Jan 2025 18:27:30 +0000 [thread overview]
Message-ID: <PRAPR10MB54224613640C377A55D8D49580E72@PRAPR10MB5422.EURPRD10.PROD.OUTLOOK.COM> (raw)
Enrolling MOK or importing platform keys is not possible without access to EFI variables.
Signed-off-by: Gokhan Cetin <gokhan.cetin@siemens.com>
---
doc/user_manual.md | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/doc/user_manual.md b/doc/user_manual.md
index 62d16c8c..bb8eb21b 100644
--- a/doc/user_manual.md
+++ b/doc/user_manual.md
@@ -1127,7 +1127,15 @@ modprobe example-module
mokutil --import /etc/sb-mok-keys/MOK/MOK.der
```
-Use the previously definded password to enroll the key, then reboot.
+Use the previously defined password to enroll the key, then reboot.
+
+If EFI variable access is disabled on kernel (due to high latencies under RT kernel),
+enrolling will result in failure `EFI variables are not supported on this system`.
+EFI variable access can be enabled by passing `efi=runtime` kernel parameter.
+
+Similarly, in cases where EFI variables are not supported, the system will not be able
+to import the keys defined on the platform in the kernel platform keyring. This will also
+result in kernel modules not being verified if they are signed with one of these platform keys.
**Boot self-signed image**:
--
2.39.2
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/PRAPR10MB54224613640C377A55D8D49580E72%40PRAPR10MB5422.EURPRD10.PROD.OUTLOOK.COM.
next reply other threads:[~2025-01-20 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 18:27 'Cetin, Gokhan' via isar-users [this message]
2025-01-21 9:40 ` 'Jan Kiszka' via isar-users
2025-02-06 7:49 ` Uladzimir Bely
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=PRAPR10MB54224613640C377A55D8D49580E72@PRAPR10MB5422.EURPRD10.PROD.OUTLOOK.COM \
--to=isar-users@googlegroups.com \
--cc=felix.moessbauer@siemens.com \
--cc=gokhan.cetin@siemens.com \
--cc=quirin.gylstorff@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox