[Group.of.nepali.translators] [Bug 1790724] Re: Backport shim 15+1533136590.3beb971-0ubuntu1 to all supported releases
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 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 ' 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 ___ 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 1790724] Re: Backport shim 15+1533136590.3beb971-0ubuntu1 to all supported releases
this has been temporarily rolled back from xenial because of the need for a matching grub update first. ** Changed in: shim (Ubuntu Xenial) Status: Fix Released => In Progress ** Changed in: shim (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: shim-signed (Ubuntu Xenial) Status: Fix Released => 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/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 Committed 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 ' 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 ___ 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 1790724] Re: Backport shim 15+1533136590.3beb971-0ubuntu1 to all supported releases
** Changed in: shim (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: shim (Ubuntu Xenial) 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/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 Released 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] == 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 ' 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 ___ 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 1790724] Re: Backport shim 15+1533136590.3beb971-0ubuntu1 to all supported releases
This bug was fixed in the package shim-signed - 1.33.1~16.04.2 --- 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 Wed, 05 Sep 2018 11:23:24 -0400 ** 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 Released 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] == 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 ' 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 ___ 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 1790724] Re: Backport shim 15+1533136590.3beb971-0ubuntu1 to all supported releases
This bug was fixed in the package shim-signed - 1.37~18.04.2 --- shim-signed (1.37~18.04.2) bionic; urgency=medium * debian/control: add Breaks: grub-efi-amd64-signed (<< 1.93.7), as the new version of shim exercises a bug in relocation code for chainload that was fixed in that upload of grub, affecting Windows 7, Windows 10, and some netboot scenarios where chainloading is required. (LP: #1792575) shim-signed (1.37~18.04.1) bionic; urgency=medium * Backport shim-signed 1.37 to Ubuntu 18.04. (LP: #1790724) shim-signed (1.37) cosmic; urgency=medium * Update to the signed 15+1533136590.3beb971-0ubuntu1 binary from Microsoft. * debian/real-po: replace debian/po to make sure things are translatable via Launchpad. -- Mathieu Trudel-Lapierre Fri, 28 Sep 2018 11:02:56 -0400 ** Changed in: shim-signed (Ubuntu Bionic) 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: New Status in shim-signed source package in Xenial: Fix Committed Status in shim source package in Bionic: Fix Committed 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] == 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 ' 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 ___ 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 1790724] Re: Backport shim 15+1533136590.3beb971-0ubuntu1 to all supported releases
This SRU has been rolled back due to functional regressions that have been reported when chainloading from shim 15 to shim 13 in MAAS. Investigation is ongoing. ** Changed in: shim-signed (Ubuntu Bionic) Status: Fix Released => Fix Committed ** Tags removed: verification-done-bionic verification-needed ** Tags added: verification-failed verification-failed-bionic -- 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: New Status in shim-signed source package in Xenial: Fix Committed Status in shim source package in Bionic: Fix Committed Status in shim-signed source package in Bionic: Fix Committed 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] == 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 ' 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 0' 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 ___ 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 1790724] Re: Backport shim 15+1533136590.3beb971-0ubuntu1 to all supported releases
This bug was fixed in the package shim-signed - 1.37~18.04.1 --- shim-signed (1.37~18.04.1) bionic; urgency=medium * Backport shim-signed 1.37 to Ubuntu 18.04. (LP: #1790724) -- Mathieu Trudel-Lapierre Tue, 04 Sep 2018 17:02:59 -0400 ** Changed in: shim-signed (Ubuntu Bionic) 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: New Status in shim-signed source package in Xenial: Fix Committed Status in shim source package in Bionic: Fix Committed 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] == 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 ' 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 0' 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 ___ 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 1790724] Re: Backport shim 15+1533136590.3beb971-0ubuntu1 to all supported releases
shim and shim-signed 15 / 1.37 are already in Cosmic. ** Also affects: shim (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: shim (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: shim (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: shim (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: shim (Ubuntu Cosmic) Status: New => Fix Released ** Also affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Changed in: shim-signed (Ubuntu Cosmic) 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/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: New Status in shim-signed source package in Xenial: New Status in shim source package in Bionic: New Status in shim-signed source package in Bionic: New 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] == 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 ' 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 0' 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 ___ 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
