https://bugzilla.suse.com/show_bug.cgi?id=1190261
https://bugzilla.suse.com/show_bug.cgi?id=1190261#c6
--- Comment #6 from Michal Suchanek ---
How do you enable secure boot?
- enable secure boot in that config and reinstall some packages (or use yast)
- reboot and enable secure boot in BIOS
-> now you have secure boot but if kernel scripts checked --sb-state you
would not be able to boot/load modules
How do you test that your problem is caused by lockdown in secure boot?
- reboot and disable secure boot in BIOS
- test stuff (1)
- reboot again to enable secure boot
- test stuff
If at (1) something checked --sb-state to determine if certificates should be
enrolled you are missing certificates and have more problems than just lockdown
now.
-> current state is irrelevant. The intention to (not) use secure boot is
expressed in that config setting, and that's the only place to look.
--
You are receiving this mail because:
You are on the CC list for the bug.