grub-install doesn't install MokManager in UEFI mode
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub2 (Ubuntu) |
Fix Released
|
Critical
|
Unassigned | ||
Precise |
Fix Released
|
Critical
|
Mathieu Trudel-Lapierre |
Bug Description
[Impact]
Precise users wanting to control Secure Boot behavior, such as disabling shim validation.
This will affect all users of DKMS packages on precise.
[Test case]
1) sudo apt-get install bbswitch-dkms ; follow steps to disable secure boot (may require proposed shim-signed 1.17~...)
2) Reboot
3) Verify that the system boots to MokManager first and prompts the user to disable Secure Boot; then successfully reboots to Ubuntu.
4) sudo modprobe -v bbswitch ; validate that the module loading is attempted and that you either get a succesful result (on systems where bbswitch is useful) or "No such device".
[Regression potential]
Given changing the logic for installing grub files; in the event that the target system detection fails grub-install may attempt to install MokManager to paths that don't exist. This will not break the system.
---
On precise; we don't currently have --target, and thus grub is also missing the logic to install MokManager to /boot/efi/
Backporting the logic to install MokManager should be fairly straightforward.
Changed in grub2 (Ubuntu): | |
importance: | Undecided → Critical |
This does not affect any release except precise.