document creation of missing signing key/certificate
Closed this issue · 0 comments
anbe42 commented
This is probably mainly a documentation issue ...
https://bugs.debian.org/1052243
There seems to be no documentation that dkms creates a key (w/o passphrase) for signing the modules if either (or both) of the files specified in mok_signing_key/mok_certificate (either defaulted, from distribution framewrok.conf or user supplied in framework.conf) are missing.
In above bug report a user supplied key/cert got overwritten (because one of the files had the wrong name in framework.conf and was therefore considered missing by dkms).