Packaging a wireless driver (rtl8814au) for secure boot

edit

If you just want the system to be able to work when Secure Boot is enabled, you might try telling shim to not enforce secure boot in later boot stages.

If you want to make the module properly work and secure boot is still enforced upon Grub & Linux kernel, you should sign your module and roll your own signing key so that it can be verified.

You can see the following links for more information:

https://ask.fedoraproject.org/en/ques...

https://access.redhat.com/documentati...hatenterpriselinux/7/html/systemadministrators_guide/sect-signing-kernel-modules-for-secure-boot

It seems that askbot corrupts links, so this is the raw links:

https://ask.fedoraproject.org/en/question/109564/how-to-get-rawhide-kernel-to-work-with-secureboot-in-f26/?answer=109840#post-id-109840

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system_administrators_guide/sect-signing-kernel-modules-for-secure-boot

@UnderMine Well no a real aswner?,Generally advanced guide for sign a kernel module isnt easy to find; because the documentation is bad (if exist), yes very bad. Exist a fronted called "UEFI-SecureBoot-SignTool"; UEFI Secure Boot Sign Tool can be used to sign kernel modules. Essentially, it is a wrapper around the sign-file binary in the kernel sources. I am testing (I need sign too), but my time is limited. Maybe we can merge forces...

You can include to your "rtl8814au" the configuration to sb-signtool...