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

[Mathieu Trudel-Lapierre]

Verified that this behaves correctly; verification-done.

** Tags removed: removal-candidate verification-needed
** Tags added: verification-done

-- 
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