I'm not sure if this is the right venue for discussion, but ever since
this change was implemented in 4.4.0-18 I have been unable to load the
VirtualBox vboxdrv kernel module built through dkms (fails with
'required key not available'). I understand this is probably the
intended behavior but because of a glitch in the bios or ssd firmware of
my laptop the secureboot mechanism is the only way I can start Ubuntu
and this has left me without an option to load custom-built modules. Is
there any mechanism to sign a kernel module through dkms? How is signing
of e.g. the nvidia module handled?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566221

Title:
  linux: Enforce signed module loading when UEFI secure boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566221/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to