https://bugzilla.redhat.com/show_bug.cgi?id=1010477
--- Comment #4 from nicolasoliver03(a)gmail.com ---
Hello,
This is still current. The Fedora documentation of secure boot is incomplete
and dated (the current one is a draft for Fedora 18)
There are some instructions on how to sign kernel modules, but it is also
inaccurate per
https://bugzilla.redhat.com/show_bug.cgi?id=1615744
Public information found by web search usually recommends nuking PK,KEK,DB,DBX
and creating your owns, which is something extreme if the only thing you want
to do is to boot a custom kernel. (e.g.
http://kroah.com/log/blog/2013/09/02/booting-a-self-signed-linux-kernel/ from
2013). This also invalidates any existing signed kernel and makes you have to
sign them with your custom keys.
It is not explained how to append a KEK and DB.
It is also not clear how kernel modules reacts to secure boot, given that the
functionality to force modules to be signed in secure boot mode comes and goes
(
https://bugzilla.redhat.com/show_bug.cgi?id=1696671)
--
You are receiving this mail because:
You are the QA Contact for the bug.