group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1790724@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package shim-signed - 1.33.1~16.04.3

---------------
shim-signed (1.33.1~16.04.3) xenial; urgency=medium

  * debian/control: Depends: on grub2 2.02~beta2-36ubuntu3.20 to ensure shim
    cannot be installed without the new grub2 version that fixes chainloading
    issues. (LP: #1792575)

shim-signed (1.33.1~16.04.2) xenial; urgency=medium

  * Update to the signed 15+1533136590.3beb971-0ubuntu1 binary from Microsoft.
    (LP: #1790724)

 -- Mathieu Trudel-Lapierre <cyphermox@xxxxxxxxxx>  Tue, 11 Dec 2018
15:37:58 -0500

** Changed in: shim-signed (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1790724

Title:
  Backport shim 15+1533136590.3beb971-0ubuntu1 to all supported releases

Status in shim package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released
Status in shim source package in Trusty:
  New
Status in shim-signed source package in Trusty:
  New
Status in shim source package in Xenial:
  Fix Committed
Status in shim-signed source package in Xenial:
  Fix Released
Status in shim source package in Bionic:
  Fix Released
Status in shim-signed source package in Bionic:
  Fix Released
Status in shim source package in Cosmic:
  Fix Released
Status in shim-signed source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  All UEFI users.

  [Test case]

  Verify that LP: #1792575 in grub has been fixed first for the corresponding release.
  == shim ==
  1) Enable Secure Boot in firmware.
  2) Update to new shim and shim-signed packages (shim 15+, shim-signed 1.37~)
  3) Validate that the system still boots and validates the shim image as well as the grub binary.

  == MokManager ==
  0) Generate a new self-signed certificate. You can use "sudo update-secureboot-policy --new-mok" for that purpose, the DER file will be in /var/lib/shim-signed/mok.
  1) Run 'sudo mokutil --enable-validation'
  2) Follow prompts on screen to enable validation if applicable.
  3) Run 'sudo mokutil --import <certificate.der>'
  4) Follow the prompts on screen to import a new certificate.
  5) Reboot
  6) Follow prompts to import the new certificate and enable validation.
  7) Validate that the system boots all the way to userland.
  8) Verify that the certificate has been correctly imported, it should be listed in the output of 'sudo mokutil --list-enrolled'.

  == mokutil ==
  1) Run 'sudo mokutil --timeout 14' (or any other arbitrary value).
  2) follow the steps for MokManager tests above.
  3) Validate that the MokManager prompt happens and shows a timeout appropriate for the timeout value set using the mokutil command.

  Also validate 'mokutil --timeout -1' works correctly, where the
  MokManager never times out.

  [Regression potential]
  Possible regressions might include failure to load shim or MokManager, or failure to validate an EFI binary (which usually translates in a Security Violation message. Any such issues should be investigated as possible regressions caused by this update.

  ---

  Backport shim to all supported releases of Ubuntu.

  Include mokutil changes to support new timeout feature.

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