This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-trusty
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
linux: Enforce signed module loading when UEFI secure boot
Status in linux package in Ubuntu:
Status in linux source package in Trusty:
Status in linux source package in Vivid:
Status in linux source package in Wily:
Status in linux source package in Xenial:
Status in linux source package in Yakkety:
This work is authorized by an approved UOS spec and blueprint at
Add code to implement secure boot checks. Unsigned or incorrectly
signed modules will continue to install while tainting the kernel
_until_ EFI_SECURE_BOOT_SIG_ENFORCE is enabled.
When EFI_SECURE_BOOT_SIG_ENFORCE is enabled, then the only recourse
for platforms booting in secure boot mode with a DKMS dependency is to
disable secure boot using mokutil:
sudo mokutil --disable-validation
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~kernel-packages
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp