-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
rhel-sst-desktop-firmware-bootloaders
-
ssg_display
-
5
-
False
-
-
None
-
None
-
None
-
None
-
None
What were you trying to do that didn't work?
In order to use systemd-sysext initrd extensions, we need to sign an extension with some key that is part of the .machine keyring.
In order to add the MOK keys into .machine (by default they are inserted into .platform), the variable MokListTrusted needs to be set, according to
https://github.com/rhboot/shim/commit/4e513405b4f1641710115780d19dcec130c5208f
https://github.com/rhboot/shim/blob/4e513405b4f1641710115780d19dcec130c5208f/MokVars.txt#L81
Steps to reproduce
- mokutil --trust-mok
- reboot and follow mok menu to make key trusted
- mokutil --import <yourkey>.der
- reboot and follow mok menu to insert the key
- verify the key is in .machine: keyctl show %:.machine
Expected results
key is in .machine keyring
Actual results
key is in .platform keyring
- impacts account
-
RHEL-19693 Signed systemd-sysext extensions for UKI initrd do not work in RHEL/Fedora/Centos
- New