[Bug 1600320] Re: grub-install doesn't install MokManager in UEFI mode

[Steve Langasek]

Hello Mathieu, or anyone else affected,

Accepted grub2 into precise-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/grub2/1.99-21ubuntu3.20 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: grub2 (Ubuntu Precise)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  grub-install doesn't install MokManager in UEFI mode

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2 source package in Precise:
  Fix Committed

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/EFI/ubuntu/ for use with shim's toggles and procedures to import signing keys.

  Backporting the logic to install MokManager should be fairly
  straightforward.

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