[Group.of.nepali.translators] [Bug 1637290] Re: Update to the signed 0.9+1474479173.6c180c6-1ubuntu1 shim binary from Microsoft

[Mathew Hodson]

This bug was fixed for Trusty in shim 0.9+1474479173.6c180c6-1ubuntu1

---
shim (0.9+1474479173.6c180c6-1ubuntu1) zesty; urgency=medium

  [ Steve Langasek ]
  * Merge (not yet NEW cleared) changes from Debian branch.

  [ Mathieu Trudel-Lapierre ]
  * debian/patches/0001-shim-fix-the-mirroring-MokSBState-fail.patch: guard
against errors in mirroring MokSBState to MokSBStateRT. Thanks to Ivan Hu
for the patch. This will fix issues updating MokSBStateRT if the variable
already exists with different attributes. (LP: #1644806)

 -- Mathieu Trudel-Lapierre  Thu, 01 Dec 2016
16:55:50 -0500

** Changed in: shim (Ubuntu Trusty)
   Status: In Progress => Fix Released

** Changed in: shim (Ubuntu Yakkety)
   Status: Won't Fix => Fix Released

** Changed in: livecd-rootfs (Ubuntu Precise)
   Status: Invalid => Won't Fix

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

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

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released
Status in grub2 source package in Precise:
  Won't Fix
Status in grub2-signed source package in Precise:
  Won't Fix
Status in livecd-rootfs source package in Precise:
  Won't Fix
Status in shim source package in Precise:
  Won't Fix
Status in shim-signed source package in Precise:
  Won't Fix
Status in grub2 source package in Trusty:
  Fix Released
Status in grub2-signed source package in Trusty:
  Fix Released
Status in livecd-rootfs source package in Trusty:
  Fix Released
Status in shim source package in Trusty:
  Fix Released
Status in shim-signed source package in Trusty:
  Fix Released
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2-signed source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  Fix Released
Status in shim-signed source package in Xenial:
  Fix Released
Status in grub2 source package in Yakkety:
  Fix Released
Status in grub2-signed source package in Yakkety:
  Fix Released
Status in livecd-rootfs source package in Yakkety:
  Fix Released
Status in shim source package in Yakkety:
  Fix Released
Status in shim-signed source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  We might want to boot securely one of these days.

  [Test case]
  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.

  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.

  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.

  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.

  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.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1637290] Re: Update to the signed 0.9+1474479173.6c180c6-1ubuntu1 shim binary from Microsoft

[Mathew Hodson]

This was fixed in Trusty.
---

shim-signed (1.32~14.04.2) trusty; urgency=medium

  * Backport shim-signed 1.32 to 14.04. (LP: #1700170)

[...]

  [ Steve Langasek ]
  * Update to the signed 0.9+1474479173.6c180c6-1ubuntu1 binary from
Microsoft.

** Changed in: shim-signed (Ubuntu Trusty)
   Status: In Progress => 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/1637290

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

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released
Status in grub2 source package in Precise:
  Won't Fix
Status in grub2-signed source package in Precise:
  Won't Fix
Status in livecd-rootfs source package in Precise:
  Invalid
Status in shim source package in Precise:
  Won't Fix
Status in shim-signed source package in Precise:
  Won't Fix
Status in grub2 source package in Trusty:
  Fix Released
Status in grub2-signed source package in Trusty:
  Fix Released
Status in livecd-rootfs source package in Trusty:
  Fix Released
Status in shim source package in Trusty:
  In Progress
Status in shim-signed source package in Trusty:
  Fix Released
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2-signed source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  Fix Released
Status in shim-signed source package in Xenial:
  Fix Released
Status in grub2 source package in Yakkety:
  Fix Released
Status in grub2-signed source package in Yakkety:
  Fix Released
Status in livecd-rootfs source package in Yakkety:
  Fix Released
Status in shim source package in Yakkety:
  Won't Fix
Status in shim-signed source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  We might want to boot securely one of these days.

  [Test case]
  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.

  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.

  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.

  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.

  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.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1637290] Re: Update to the signed 0.9+1474479173.6c180c6-1ubuntu1 shim binary from Microsoft

[Mathieu Trudel-Lapierre]

** Changed in: shim (Ubuntu Yakkety)
   Status: In Progress => Won't Fix

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

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

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released
Status in grub2 source package in Precise:
  Won't Fix
Status in grub2-signed source package in Precise:
  Won't Fix
Status in livecd-rootfs source package in Precise:
  Invalid
Status in shim source package in Precise:
  Won't Fix
Status in shim-signed source package in Precise:
  Won't Fix
Status in grub2 source package in Trusty:
  Fix Released
Status in grub2-signed source package in Trusty:
  Fix Released
Status in livecd-rootfs source package in Trusty:
  Fix Released
Status in shim source package in Trusty:
  In Progress
Status in shim-signed source package in Trusty:
  In Progress
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2-signed source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  Fix Released
Status in shim-signed source package in Xenial:
  Fix Released
Status in grub2 source package in Yakkety:
  Fix Released
Status in grub2-signed source package in Yakkety:
  Fix Released
Status in livecd-rootfs source package in Yakkety:
  Fix Released
Status in shim source package in Yakkety:
  Won't Fix
Status in shim-signed source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  We might want to boot securely one of these days.

  [Test case]
  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.

  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.

  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.

  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.

  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.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1637290] Re: Update to the signed 0.9+1474479173.6c180c6-1ubuntu1 shim binary from Microsoft

[Brian Murray]

** Changed in: shim (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/1637290

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

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released
Status in grub2 source package in Precise:
  Won't Fix
Status in grub2-signed source package in Precise:
  Won't Fix
Status in livecd-rootfs source package in Precise:
  Invalid
Status in shim source package in Precise:
  Won't Fix
Status in shim-signed source package in Precise:
  Won't Fix
Status in grub2 source package in Trusty:
  Fix Released
Status in grub2-signed source package in Trusty:
  Fix Released
Status in livecd-rootfs source package in Trusty:
  Fix Released
Status in shim source package in Trusty:
  In Progress
Status in shim-signed source package in Trusty:
  In Progress
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2-signed source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  Fix Released
Status in shim-signed source package in Xenial:
  Fix Released
Status in grub2 source package in Yakkety:
  Fix Released
Status in grub2-signed source package in Yakkety:
  Fix Released
Status in livecd-rootfs source package in Yakkety:
  Fix Released
Status in shim source package in Yakkety:
  Won't Fix
Status in shim-signed source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  We might want to boot securely one of these days.

  [Test case]
  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.

  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.

  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.

  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.

  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.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1637290] Re: Update to the signed 0.9+1474479173.6c180c6-1ubuntu1 shim binary from Microsoft

[Mathieu Trudel-Lapierre]

Trusty's livecd-rootfs also already carries the fix here to not copy
again over grub's images, and use grub-install:

https://launchpad.net/ubuntu/+source/livecd-rootfs/2.208.14

"* ubuntu-cpc: Remove redundant copy of grub files."

** Changed in: livecd-rootfs (Ubuntu Trusty)
   Status: New => 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/1637290

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

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released
Status in grub2 source package in Precise:
  Won't Fix
Status in grub2-signed source package in Precise:
  Won't Fix
Status in livecd-rootfs source package in Precise:
  Invalid
Status in shim source package in Precise:
  Won't Fix
Status in shim-signed source package in Precise:
  Won't Fix
Status in grub2 source package in Trusty:
  Fix Released
Status in grub2-signed source package in Trusty:
  Fix Released
Status in livecd-rootfs source package in Trusty:
  Fix Released
Status in shim source package in Trusty:
  In Progress
Status in shim-signed source package in Trusty:
  In Progress
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2-signed source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  Fix Committed
Status in shim-signed source package in Xenial:
  Fix Released
Status in grub2 source package in Yakkety:
  Fix Released
Status in grub2-signed source package in Yakkety:
  Fix Released
Status in livecd-rootfs source package in Yakkety:
  Fix Released
Status in shim source package in Yakkety:
  In Progress
Status in shim-signed source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  We might want to boot securely one of these days.

  [Test case]
  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.

  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.

  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.

  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.

  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.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1637290] Re: Update to the signed 0.9+1474479173.6c180c6-1ubuntu1 shim binary from Microsoft

[Steve Langasek]

** Changed in: grub2-signed (Ubuntu Precise)
   Status: New => Won't Fix

** Changed in: shim (Ubuntu Precise)
   Status: New => Won't Fix

** Changed in: shim-signed (Ubuntu Precise)
   Status: New => Won't Fix

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

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

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released
Status in grub2 source package in Precise:
  Won't Fix
Status in grub2-signed source package in Precise:
  Won't Fix
Status in livecd-rootfs source package in Precise:
  Invalid
Status in shim source package in Precise:
  Won't Fix
Status in shim-signed source package in Precise:
  Won't Fix
Status in grub2 source package in Trusty:
  Fix Released
Status in grub2-signed source package in Trusty:
  Fix Released
Status in livecd-rootfs source package in Trusty:
  New
Status in shim source package in Trusty:
  In Progress
Status in shim-signed source package in Trusty:
  In Progress
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2-signed source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  Fix Committed
Status in shim-signed source package in Xenial:
  Fix Released
Status in grub2 source package in Yakkety:
  Fix Released
Status in grub2-signed source package in Yakkety:
  Fix Released
Status in livecd-rootfs source package in Yakkety:
  Fix Released
Status in shim source package in Yakkety:
  In Progress
Status in shim-signed source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  We might want to boot securely one of these days.

  [Test case]
  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.

  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.

  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.

  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.

  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.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1637290] Re: Update to the signed 0.9+1474479173.6c180c6-1ubuntu1 shim binary from Microsoft

[Launchpad Bug Tracker]

This bug was fixed in the package grub2 - 2.02~beta2-9ubuntu1.14

---
grub2 (2.02~beta2-9ubuntu1.14) trusty; urgency=medium

  * debian/patches/install_signed.patch: update to use the new names for the
shim binary (shim$arch) and MokManager (mm$arch). (LP: #1637290)
  * debian/control: Breaks shim (<< 0.9+1474479173.6c180c6-0ubuntu1~) for the
renamed EFI binaries.

 -- Mathieu Trudel-Lapierre   Fri, 14 Jul 2017
12:20:11 -0400

** Changed in: grub2 (Ubuntu Trusty)
   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/1637290

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

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released
Status in grub2 source package in Precise:
  Won't Fix
Status in grub2-signed source package in Precise:
  New
Status in livecd-rootfs source package in Precise:
  Invalid
Status in shim source package in Precise:
  New
Status in shim-signed source package in Precise:
  New
Status in grub2 source package in Trusty:
  Fix Released
Status in grub2-signed source package in Trusty:
  Fix Released
Status in livecd-rootfs source package in Trusty:
  New
Status in shim source package in Trusty:
  In Progress
Status in shim-signed source package in Trusty:
  In Progress
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2-signed source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  Fix Committed
Status in shim-signed source package in Xenial:
  Fix Released
Status in grub2 source package in Yakkety:
  Fix Released
Status in grub2-signed source package in Yakkety:
  Fix Released
Status in livecd-rootfs source package in Yakkety:
  Fix Released
Status in shim source package in Yakkety:
  In Progress
Status in shim-signed source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  We might want to boot securely one of these days.

  [Test case]
  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.

  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.

  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.

  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.

  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.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1637290] Re: Update to the signed 0.9+1474479173.6c180c6-1ubuntu1 shim binary from Microsoft

[Launchpad Bug Tracker]

This bug was fixed in the package grub2-signed - 1.34.16

---
grub2-signed (1.34.16) trusty; urgency=medium

  * Rebuild against grub-efi-amd64 2.02~beta2-9ubuntu1.14 (LP: #1637290)

 -- Mathieu Trudel-Lapierre   Fri, 14 Jul 2017
15:33:38 -0400

** Changed in: grub2-signed (Ubuntu Trusty)
   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/1637290

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

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released
Status in grub2 source package in Precise:
  Won't Fix
Status in grub2-signed source package in Precise:
  New
Status in livecd-rootfs source package in Precise:
  Invalid
Status in shim source package in Precise:
  New
Status in shim-signed source package in Precise:
  New
Status in grub2 source package in Trusty:
  Fix Released
Status in grub2-signed source package in Trusty:
  Fix Released
Status in livecd-rootfs source package in Trusty:
  New
Status in shim source package in Trusty:
  In Progress
Status in shim-signed source package in Trusty:
  In Progress
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2-signed source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  Fix Committed
Status in shim-signed source package in Xenial:
  Fix Released
Status in grub2 source package in Yakkety:
  Fix Released
Status in grub2-signed source package in Yakkety:
  Fix Released
Status in livecd-rootfs source package in Yakkety:
  Fix Released
Status in shim source package in Yakkety:
  In Progress
Status in shim-signed source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  We might want to boot securely one of these days.

  [Test case]
  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.

  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.

  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.

  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.

  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.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1637290] Re: Update to the signed 0.9+1474479173.6c180c6-1ubuntu1 shim binary from Microsoft

[Steve Langasek]

Hello Mathieu, or anyone else affected,

Accepted grub2 into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/grub2/2.02~beta2-9ubuntu1.14 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 on 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-trusty to verification-done-trusty. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-trusty. 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: New => Won't Fix

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

** Tags added: verification-needed verification-needed-trusty

** Changed in: grub2-signed (Ubuntu Trusty)
   Status: In Progress => Fix Committed

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

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

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released
Status in grub2 source package in Precise:
  Won't Fix
Status in grub2-signed source package in Precise:
  New
Status in livecd-rootfs source package in Precise:
  Invalid
Status in shim source package in Precise:
  New
Status in shim-signed source package in Precise:
  New
Status in grub2 source package in Trusty:
  Fix Committed
Status in grub2-signed source package in Trusty:
  Fix Committed
Status in livecd-rootfs source package in Trusty:
  New
Status in shim source package in Trusty:
  In Progress
Status in shim-signed source package in Trusty:
  In Progress
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2-signed source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  Fix Committed
Status in shim-signed source package in Xenial:
  Fix Released
Status in grub2 source package in Yakkety:
  Fix Released
Status in grub2-signed source package in Yakkety:
  Fix Released
Status in livecd-rootfs source package in Yakkety:
  Fix Released
Status in shim source package in Yakkety:
  In Progress
Status in shim-signed source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  We might want to boot securely one of these days.

  [Test case]
  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.

  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.

  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.

  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.

  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.

To manage notifications 

[Group.of.nepali.translators] [Bug 1637290] Re: Update to the signed 0.9+1474479173.6c180c6-1ubuntu1 shim binary from Microsoft

[Robert C Jennings]

** Branch linked: lp:~rcj/livecd-rootfs/trusty-proposed_ubuntu-cpc

** Changed in: livecd-rootfs (Ubuntu Trusty)
   Status: Invalid => New

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

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

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released
Status in grub2 source package in Precise:
  New
Status in grub2-signed source package in Precise:
  New
Status in livecd-rootfs source package in Precise:
  Invalid
Status in shim source package in Precise:
  New
Status in shim-signed source package in Precise:
  New
Status in grub2 source package in Trusty:
  In Progress
Status in grub2-signed source package in Trusty:
  In Progress
Status in livecd-rootfs source package in Trusty:
  New
Status in shim source package in Trusty:
  In Progress
Status in shim-signed source package in Trusty:
  In Progress
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2-signed source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  Fix Committed
Status in shim-signed source package in Xenial:
  Fix Released
Status in grub2 source package in Yakkety:
  Fix Released
Status in grub2-signed source package in Yakkety:
  Fix Released
Status in livecd-rootfs source package in Yakkety:
  Fix Released
Status in shim source package in Yakkety:
  In Progress
Status in shim-signed source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  We might want to boot securely one of these days.

  [Test case]
  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.

  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.

  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.

  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.

  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.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1637290] Re: Update to the signed 0.9+1474479173.6c180c6-1ubuntu1 shim binary from Microsoft

[Launchpad Bug Tracker]

This bug was fixed in the package shim-signed - 1.27~16.04.1

---
shim-signed (1.27~16.04.1) xenial; urgency=medium

  * Backport shim 0.9+1474479173.6c180c6-1ubuntu1 to 16.04. (LP:
#1637290)

shim-signed (1.27) zesty; urgency=medium

  [ Steve Langasek ]
  * Update to the signed 0.9+1474479173.6c180c6-1ubuntu1 binary from
Microsoft.
  * update-secureboot-policy:
- detect when we have no debconf prompting and error out instead of ending
  up in an infinite loop.  LP: #1673817.
- refactor to make the code easier to follow.
- remove a confusing boolean that would always re-prompt on a request to
  --enable, but not on a request to --disable.

  [ Mathieu Trudel-Lapierre ]
  * update-secureboot-policy:
- some more fixes to properly handle non-interactive mode. (LP: #1673817)

shim-signed (1.23) zesty; urgency=medium

  * debian/control: bump the Depends on grub2-common since that's needed to
install with the new updated EFI binaries filenames.

shim-signed (1.22) yakkety; urgency=medium

  * Update to the signed 0.9+1474479173.6c180c6-0ubuntu1 binary from Microsoft.
(LP: #1581299)
  * Update paths now that the shim binary has been renamed to include the
target architecture.
  * debian/shim-signed.postinst: clean up old MokManager.efi from EFI/ubuntu;
since it's being replaced by mm$arch.efi.

 -- Mathieu Trudel-Lapierre   Thu, 23 Mar 2017
16:58:44 -0400

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

** Changed in: grub2 (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/1637290

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

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released
Status in grub2 source package in Precise:
  New
Status in grub2-signed source package in Precise:
  New
Status in livecd-rootfs source package in Precise:
  Invalid
Status in shim source package in Precise:
  New
Status in shim-signed source package in Precise:
  New
Status in grub2 source package in Trusty:
  In Progress
Status in grub2-signed source package in Trusty:
  In Progress
Status in livecd-rootfs source package in Trusty:
  Invalid
Status in shim source package in Trusty:
  In Progress
Status in shim-signed source package in Trusty:
  In Progress
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2-signed source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  Fix Committed
Status in shim-signed source package in Xenial:
  Fix Released
Status in grub2 source package in Yakkety:
  Fix Released
Status in grub2-signed source package in Yakkety:
  Fix Released
Status in livecd-rootfs source package in Yakkety:
  Fix Released
Status in shim source package in Yakkety:
  In Progress
Status in shim-signed source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  We might want to boot securely one of these days.

  [Test case]
  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.

  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.

  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.

  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.

  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 

[Group.of.nepali.translators] [Bug 1637290] Re: Update to the signed 0.9+1474479173.6c180c6-1ubuntu1 shim binary from Microsoft

[Launchpad Bug Tracker]

This bug was fixed in the package grub2 - 2.02~beta2-36ubuntu3.9

---
grub2 (2.02~beta2-36ubuntu3.9) xenial; urgency=medium

  * debian/patches/install_signed.patch: update to use the new names for the
shim binary (shim$arch), MokManager (mm$arch) and add fallback (fb$arch).
(LP: #1637290)
  * debian/control: Breaks shim (<< 0.9+1474479173.6c180c6-0ubuntu1~) for the
renamed EFI binaries.

 -- Mathieu Trudel-Lapierre   Tue, 08 Nov 2016
14:42:24 -0500

** Changed in: grub2-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/1637290

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

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released
Status in grub2 source package in Precise:
  New
Status in grub2-signed source package in Precise:
  New
Status in livecd-rootfs source package in Precise:
  Invalid
Status in shim source package in Precise:
  New
Status in shim-signed source package in Precise:
  New
Status in grub2 source package in Trusty:
  In Progress
Status in grub2-signed source package in Trusty:
  In Progress
Status in livecd-rootfs source package in Trusty:
  Invalid
Status in shim source package in Trusty:
  In Progress
Status in shim-signed source package in Trusty:
  In Progress
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2-signed source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  Fix Committed
Status in shim-signed source package in Xenial:
  Fix Released
Status in grub2 source package in Yakkety:
  Fix Released
Status in grub2-signed source package in Yakkety:
  Fix Released
Status in livecd-rootfs source package in Yakkety:
  Fix Released
Status in shim source package in Yakkety:
  In Progress
Status in shim-signed source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  We might want to boot securely one of these days.

  [Test case]
  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.

  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.

  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.

  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.

  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.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1637290] Re: Update to the signed 0.9+1474479173.6c180c6-1ubuntu1 shim binary from Microsoft

[Launchpad Bug Tracker]

This bug was fixed in the package grub2 - 2.02~beta2-36ubuntu11.2

---
grub2 (2.02~beta2-36ubuntu11.2) yakkety; urgency=medium

  * debian/patches/install_signed.patch: update to use the new names for the
shim binary (shim$arch), MokManager (mm$arch) and add fallback (fb$arch).
(LP: #1637290)
  * debian/control: Breaks shim (<< 0.9+1474479173.6c180c6-0ubuntu1~) for the
renamed EFI binaries.

 -- Mathieu Trudel-Lapierre   Thu, 22 Sep 2016
12:34:56 -0400

** Changed in: grub2-signed (Ubuntu Yakkety)
   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/1637290

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

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released
Status in grub2 source package in Precise:
  New
Status in grub2-signed source package in Precise:
  New
Status in livecd-rootfs source package in Precise:
  Invalid
Status in shim source package in Precise:
  New
Status in shim-signed source package in Precise:
  New
Status in grub2 source package in Trusty:
  In Progress
Status in grub2-signed source package in Trusty:
  In Progress
Status in livecd-rootfs source package in Trusty:
  Invalid
Status in shim source package in Trusty:
  In Progress
Status in shim-signed source package in Trusty:
  In Progress
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2-signed source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  Fix Committed
Status in shim-signed source package in Xenial:
  Fix Released
Status in grub2 source package in Yakkety:
  Fix Released
Status in grub2-signed source package in Yakkety:
  Fix Released
Status in livecd-rootfs source package in Yakkety:
  Fix Released
Status in shim source package in Yakkety:
  In Progress
Status in shim-signed source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  We might want to boot securely one of these days.

  [Test case]
  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.

  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.

  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.

  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.

  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.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1637290] Re: Update to the signed 0.9+1474479173.6c180c6-1ubuntu1 shim binary from Microsoft

[Launchpad Bug Tracker]

This bug was fixed in the package shim-signed - 1.27~16.10.1

---
shim-signed (1.27~16.10.1) yakkety; urgency=medium

  * Backport shim 0.9+1474479173.6c180c6-1ubuntu1 to 16.10. (LP:
#1637290)

shim-signed (1.27) zesty; urgency=medium

  [ Steve Langasek ]
  * Update to the signed 0.9+1474479173.6c180c6-1ubuntu1 binary from
Microsoft.
  * update-secureboot-policy:
- detect when we have no debconf prompting and error out instead of ending
  up in an infinite loop.  LP: #1673817.
- refactor to make the code easier to follow.
- remove a confusing boolean that would always re-prompt on a request to
  --enable, but not on a request to --disable.

  [ Mathieu Trudel-Lapierre ]
  * update-secureboot-policy:
- some more fixes to properly handle non-interactive mode. (LP: #1673817)

shim-signed (1.23) zesty; urgency=medium

  * debian/control: bump the Depends on grub2-common since that's needed to
install with the new updated EFI binaries filenames.

shim-signed (1.22) yakkety; urgency=medium

  * Update to the signed 0.9+1474479173.6c180c6-0ubuntu1 binary from Microsoft.
(LP: #1581299)
  * Update paths now that the shim binary has been renamed to include the
target architecture.
  * debian/shim-signed.postinst: clean up old MokManager.efi from EFI/ubuntu;
since it's being replaced by mm$arch.efi.

 -- Mathieu Trudel-Lapierre   Thu, 23 Mar 2017
16:58:44 -0400

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

** Changed in: grub2 (Ubuntu Yakkety)
   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/1637290

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

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released
Status in grub2 source package in Precise:
  New
Status in grub2-signed source package in Precise:
  New
Status in livecd-rootfs source package in Precise:
  Invalid
Status in shim source package in Precise:
  New
Status in shim-signed source package in Precise:
  New
Status in grub2 source package in Trusty:
  In Progress
Status in grub2-signed source package in Trusty:
  In Progress
Status in livecd-rootfs source package in Trusty:
  Invalid
Status in shim source package in Trusty:
  In Progress
Status in shim-signed source package in Trusty:
  In Progress
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2-signed source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  Fix Committed
Status in shim-signed source package in Xenial:
  Fix Released
Status in grub2 source package in Yakkety:
  Fix Released
Status in grub2-signed source package in Yakkety:
  Fix Released
Status in livecd-rootfs source package in Yakkety:
  Fix Released
Status in shim source package in Yakkety:
  In Progress
Status in shim-signed source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  We might want to boot securely one of these days.

  [Test case]
  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.

  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.

  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.

  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.

  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 

[Group.of.nepali.translators] [Bug 1637290] Re: Update to the signed 0.9+1474479173.6c180c6-1ubuntu1 shim binary from Microsoft

[Launchpad Bug Tracker]

This bug was fixed in the package livecd-rootfs - 2.408.9

---
livecd-rootfs (2.408.9) xenial; urgency=medium

  [ Daniel Watkins ]
  * Don't overwrite the default sources.list in cloud images.
  * Replace sources.list generated using COMPONENTS with the sources.list from
an Ubuntu Server installation (i.e. with all components enabled, and all
deb-src lines commented).  LP: #1513529.

  [ Chris Glass ]
  * Fix the manifest generation in OVA files so that ovf files don't have
double extensions.  (LP: #1627931)
  * Fix the OVF's metadata to include Ubuntu specific identifiers and
descriptions instead of the generic Linux ones.  (LP: #1656293)

  [ Daniel Watkins ]
  * Add replace_grub_root_with_label function thereby consolidating multiple
uses of the same calls to sed.

  [ Robert C Jennings ]
  * ubuntu-cpc: Remove redundant copy of grub files. (LP: #1637290)

 -- Robert C Jennings   Thu, 23 Mar 2017
14:40:59 -0400

** Changed in: livecd-rootfs (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/1637290

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

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released
Status in grub2 source package in Precise:
  New
Status in grub2-signed source package in Precise:
  New
Status in livecd-rootfs source package in Precise:
  Invalid
Status in shim source package in Precise:
  New
Status in shim-signed source package in Precise:
  New
Status in grub2 source package in Trusty:
  In Progress
Status in grub2-signed source package in Trusty:
  In Progress
Status in livecd-rootfs source package in Trusty:
  Invalid
Status in shim source package in Trusty:
  In Progress
Status in shim-signed source package in Trusty:
  In Progress
Status in grub2 source package in Xenial:
  Fix Committed
Status in grub2-signed source package in Xenial:
  Fix Committed
Status in livecd-rootfs source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  Fix Committed
Status in shim-signed source package in Xenial:
  Fix Committed
Status in grub2 source package in Yakkety:
  Fix Committed
Status in grub2-signed source package in Yakkety:
  Fix Committed
Status in livecd-rootfs source package in Yakkety:
  Fix Released
Status in shim source package in Yakkety:
  In Progress
Status in shim-signed source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  We might want to boot securely one of these days.

  [Test case]
  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.

  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.

  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.

  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.

  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.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to :