Secure Boot is a feature that landed in Fedora 18 and above related securing the boot stages on EFI firmware and required by Windows 10+.
With Fedora 36+, the akmods package have support to automatically sign locally built kmod with a self generated key. Such key must be imported into the EFI firmware (you must have right to access the EFI firmware).
It's not required to disable secure boot (not even move to BIOS compatibility).
Securing your key
Because the Secure Boot key is available locally on your computer, (by default it's in /etc/pki/akmods) you might need to consider encrypting your rootfs as appropriate in order to protect the key. Please consider this as a mandatory requirement, or consider to transfer the key to an external (and secure) location. or even use an hardware token
Importing the key
As per the README.secureboot (located at /usr/share/doc/akmods/README.secureboot) you need the following commands:
# To create the self generated key and certificate: /usr/sbin/kmodgenca # To import the key, the command will ask for a password to protect the key # You will have to enter this password during the special EFI window mokutil --import /etc/pki/akmods/certs/public_key.der
How to disable Secure Boot
It's still possible to disable secure boot from the EFI firmware.
How to use Secure Boot with a self compiled kernel ?
It's still WIP, but then 3rd part kmod signature won't work. This is worked on at https://bugzilla.redhat.com/show_bug.cgi?id=2070866
* Fedora initial feature on Secure boot
* Another RFE related to how to deal with Secure Boot for 3rd part kmod