After seeing into the process of signing DKMS modules, I confirm that
creating the keys and configuring DKMS to sign modules after building is
not configured in the modules packages.
Closing the bug as invalid.
** Changed in: acpi-call (Ubuntu)
Status: New => Invalid
--
You received
Mmmh, a search through sources.debian.net indicates that this path is
mentioned in the source code of packages dkms and virtualbox.
https://codesearch.debian.net/search?q=%2Fvar%2Flib%2Fshim-
signed%2Fmok%2FMOK.der
I guess that DKMS creates the certificate, and VirtualBox seems able to
use it.
I did not create the /var/lib/shim-signed/mok/MOK.der key : I only located it
using "locate *.der".
I guess some package created it (though "dpkg -S" knows nothing about it).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
thanks for the report.
I admit that, since I didn't own an UEFI machine until recently, I never
looked in the secure boot process.
Now that I do, I need to determine if this signature is supposed to be
done by the packages modules themselves, by DKMS once and for all, or
manually by the
Manually executing
sudo mokutil --import /var/lib/shim-signed/mok/MOK.der
then rebooting and enrolling the key solved the problem.
But I guess that should have been done automatically?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
