TRUSTY:

Cases 1 and 2 (upgrade and booting normally) are verified.

Case 4 is verified (created a new EFI BootEntry calling MokManager: sudo
efibootmgr -c -L Mok -l \\EFI\\ubuntu\\shimx64.efi -u \\mmx64.efi).

Network boot is still left to be verified.

** Description changed:

  [Impact]
  We might want to boot securely one of these days.
  
  [Test case]
- A) Upgrading
+ 1) Upgrading
  - Update to new shim, shim-signed, grub2, grub2-signed on an UEFI system.
  - Verify that the new shimx64.efi file is under /boot/efi/EFI/ubuntu, along 
with mmx64.efi and fbx64.efi.
  - Verify that /boot/efi/EFI/ubuntu/MokManager.efi no longer exists.
  - Verify that trying to apt install grub alone, or apt install shim alone, 
pulls in the correct matching versions of packages and gives the same results.
  
- B) Booting normally
+ 2) Booting normally
  - Update to new shim, shim-signed, grub2, grub2-signed on an UEFI system, 
with Secure Boot enabled.
  - Verify it boots successfully to the login prompt.
  - There should be no messages about "Verification failure" or other errors 
before the kernel is loaded.
  
- C) Network boot.
+ 3) Network boot.
  - Update to shim signed and grub2 signed EFI binaries on the TFTP server used.
  - Verify that a network booting system still boots normally through shim and 
grub, reaching a login prompt.
  
- D) BootEntry options
+ 4) BootEntry options
  - Update to new shim, shim-signed, grub2, grub2-signed on an UEFI system.
  - Update or install fwupdate.
  - Verify that new updates can be applied via fwupdate, that when an update is 
available, fwupdate will correctly start, apply the update, and reboot to shim 
normally, leading to a working system.
  
- E) live builds
+ 5) live builds
  - confirm that the new version of livecd-rootfs has been published to 
-updates first, and that a daily build of the UEFI-enabled cloud images 
succeeds with the new shim filenames.
- 
  
  [Regression Potential]
  Any failure to load the kernel from grub, or for shim to load grub, or for 
the system firmware to load shim (such as "Verification failure" messages) or 
failure to retrieve or parse BootEntry extended options (such as necessary to 
load MokManager or fwupdate) should be considered regressions.

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

Title:
  Update to the signed 0.9+1474479173.6c180c6-0ubuntu1 shim binary from
  Microsoft

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

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

Reply via email to