[Bug 1890835] Re: secureboot-db 2020 update
A newer dbx update has been published, thus this version should not go out to updates & security. The new update requires SBAT capable shim, which is in progress being rolled out at the moment. ** Tags removed: verification-needed-bionic verification-needed-focal verification-needed-xenial ** Tags added: verification-failed-bionic verification-failed-focal verification-failed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890835 Title: secureboot-db 2020 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/secureboot-db/+bug/1890835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890835] Re: secureboot-db 2020 update
** Changed in: secureboot-db (Ubuntu) Importance: Undecided => Medium ** Changed in: secureboot-db (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: secureboot-db (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: secureboot-db (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: secureboot-db (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: secureboot-db (Ubuntu Groovy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890835 Title: secureboot-db 2020 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/secureboot-db/+bug/1890835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890835] Re: secureboot-db 2020 update
Removed the verification-failed tags so that this bug doesn't show up in the -proposed cleanup report of packages to remove from -proposed. ** Tags removed: block-proposed-groovy verification-failed-bionic verification-failed-focal verification-failed-xenial verification-needed ** Tags added: verification-needed-bionic verification-needed-focal verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890835 Title: secureboot-db 2020 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/secureboot-db/+bug/1890835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890835] Re: secureboot-db 2020 update
Based on comment #15, I assume the same deb will be released again to focal-updates, Ubuntu only roll it back to focal-proposed to provide Feodra community has more time to address the problem. If it's an Ubuntu only machines, users are free and allowed to use the same deb right now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890835 Title: secureboot-db 2020 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/secureboot-db/+bug/1890835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890835] Re: secureboot-db 2020 update
** Tags added: block-proposed-focal block-proposed-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890835 Title: secureboot-db 2020 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/secureboot-db/+bug/1890835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890835] Re: secureboot-db 2020 update
The focal SRU has been rolled back for the time being from focal-updates to focal-proposed, due to compatibility concerns with current Fedora. They will be re-released at a later date. For the time being I am marking verification-failed to block promotion, but this does not mean they should be removed from -proposed. ** Changed in: secureboot-db (Ubuntu Focal) Status: Fix Released => Fix Committed ** Tags removed: verification-done-focal verification-needed-bionic verification-needed-xenial ** Tags added: verification-failed-bionic verification-failed-focal verification-failed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890835 Title: secureboot-db 2020 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/secureboot-db/+bug/1890835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890835] Re: secureboot-db 2020 update
"Yes, ESM will be poked after other series release this." Dimitri - do we plan to respin trusty media with the upgraded grub? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890835 Title: secureboot-db 2020 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/secureboot-db/+bug/1890835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890835] Re: secureboot-db 2020 update
This bug was fixed in the package secureboot-db - 1.6~20.04.1 --- secureboot-db (1.6~20.04.1) focal; urgency=medium * Ship MS 2020 split arch dbx updates. LP: #1890835 * Add arm64 architecture. * Add breaks on grub-efi-$arch-signed less than security pocket. -- Dimitri John Ledkov Fri, 24 Jul 2020 00:34:57 +0100 ** Changed in: secureboot-db (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890835 Title: secureboot-db 2020 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/secureboot-db/+bug/1890835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890835] Re: secureboot-db 2020 update
Publishing secureboot-db for focal-updates and focal-security. As discussed, this is fine to go to -security too as it the package is basically a 'pure data' package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890835 Title: secureboot-db 2020 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/secureboot-db/+bug/1890835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890835] Re: secureboot-db 2020 update
Slow phasing is merged and deployed now. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890835 Title: secureboot-db 2020 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/secureboot-db/+bug/1890835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890835] Re: secureboot-db 2020 update
Booted 20.04.1 ISO, in a 4k ovmf qemu KVM VM with secureboot MS keys and installed secureboot-db from focal-proposed, checking in journalctl that dbxupdate from 1.6~20.04.1 got applied. Shut down the VM. Attempted to boot 20.04 BETA iso, and it failed to boot with Verification failed Security Violation. Thus dbx update was correctly applied and vulnerable OS can no longer boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890835 Title: secureboot-db 2020 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/secureboot-db/+bug/1890835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890835] Re: secureboot-db 2020 update
Yes, ESM will be poked after other series release this. ** Tags removed: block-proposed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890835 Title: secureboot-db 2020 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/secureboot-db/+bug/1890835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890835] Re: secureboot-db 2020 update
Someone will have to poke the ESM team to take care of trusty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890835 Title: secureboot-db 2020 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/secureboot-db/+bug/1890835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890835] Re: secureboot-db 2020 update
Hello Dimitri, or anyone else affected, Accepted secureboot-db into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/secureboot- db/1.4.1 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, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: secureboot-db (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic ** Changed in: secureboot-db (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890835 Title: secureboot-db 2020 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/secureboot-db/+bug/1890835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890835] Re: secureboot-db 2020 update
Hello Dimitri, or anyone else affected, Accepted secureboot-db into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/secureboot- db/1.6~20.04.1 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, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: secureboot-db (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890835 Title: secureboot-db 2020 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/secureboot-db/+bug/1890835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890835] Re: secureboot-db 2020 update
** Tags added: id-57571331a85e0e034520474d -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890835 Title: secureboot-db 2020 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/secureboot-db/+bug/1890835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890835] Re: secureboot-db 2020 update
Reuploaded with breaks on versions of signed grubs less than those in the security pocket. This however may introduce an inverse problem of attempting to either remove signed grub, or remove secureboot-db, to resolve the conflict if for some reason users prohibit upgrading the signed grub packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890835 Title: secureboot-db 2020 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/secureboot-db/+bug/1890835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890835] Re: secureboot-db 2020 update
Apologies if this is completely not a thing, but I'm a bit worried about cases where people install the secureboot-db update but still have the old grub2 installed (as there is no breaks). Will that cause a problem? Since if I understand it (but I might be wrong), wouldn't they be unable to boot their systems anymore? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890835 Title: secureboot-db 2020 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/secureboot-db/+bug/1890835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890835] Re: secureboot-db 2020 update
** Description changed: + NB! do not release this update to -updates, until slow phasing is + available, at 4% per day. + + NB! ideally phase one series at the time, to ensure we can deal with a + flood of support requests if any arise. + [Impact] * Ship 2020 dbxupdate from MS [Test Case] - * In case of multi-boot systems, please plan to boot into every + * In case of multi-boot systems, please plan to boot into every operating system on your multi-boot systems and install updates as soon as your other operating system distributions publish updates for BootHole vulnerability. * Install package on Secureboot UEFI enabled system * Reboot * Observe that it still reboots [Regression Potential] * Installing this package even once will update DBX variable in the UEFI firmware and will prevent booting: - All Ubuntu, Debian, RHEL, Fedora, OpenSUSE, SUSE, Oracle Linux milestones / media released before August 2020 - Certain version of Kaspersky Labs UEFI protect software - Certain version of HPE Inc ProLiant automatic OS provisioning As they are all vulnerable to the BootHole vunlerability. For example, one will have to use 16.04.7 LTS, 18.04.5 LTS, 20.04.1 LTS installer media if they want to reinstall. If any dual boot configurations are failing to boot, one must navigated to UEFI BIOS settings and either reset DBX variables to stock values, or disable secureboot. Upgrade any systems that are now prohibited to boot. And then re-enable secureboot & reinstall secureboot-db package to reapply dbx updates. Please note simple downgrade of secureboot-db package will not achieve anything, as downgrading the package does not revert the firmware changes. [Other Info] * For more inforamtion please see https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/GRUB2SecureBootBypass -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890835 Title: secureboot-db 2020 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/secureboot-db/+bug/1890835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890835] Re: secureboot-db 2020 update
** Description changed: - secureboot-db 2020 update + [Impact] - Expecting long period in -proposed. + * Ship 2020 dbxupdate from MS - Test to ensure certified laptops are not bricked before publishing to - updates. + [Test Case] - Expecting slow phasing in -updates, at 4% a day, 25 days in total. + * Install package on Secureboot UEFI enabled system + * Reboot + * Observe that it still reboots + + [Regression Potential] + + * Installing this package even once will update DBX variable in the + UEFI firmware and will prevent booting: + + - All Ubuntu, Debian, RHEL, Fedora, OpenSUSE, SUSE, Oracle Linux milestones / media released before August 2020 + - Certain version of Kaspersky Labs UEFI protect software + - Certain version of HPE Inc ProLiant automatic OS provisioning + + As they are all vulnerable to the BootHole vunlerability. + + For example, one will have to use 16.04.7 LTS, 18.04.5 LTS, 20.04.1 LTS + installer media if they want to reinstall. + + If any dual boot configurations are failing to boot, one must navigated + to UEFI BIOS settings and either reset DBX variables to stock values, or + disable secureboot. Upgrade any systems that are now prohibited to boot. + And then re-enable secureboot & reinstall secureboot-db package to + reapply dbx updates. + + Please note simple downgrade of secureboot-db package will not achieve + anything, as downgrading the package does not revert the firmware + changes. + + [Other Info] + + * For more inforamtion please see https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/GRUB2SecureBootBypass ** Description changed: [Impact] - * Ship 2020 dbxupdate from MS + * Ship 2020 dbxupdate from MS [Test Case] - * Install package on Secureboot UEFI enabled system - * Reboot - * Observe that it still reboots + * In case of multi-boot systems, please plan to boot into every + operating system on your multi-boot systems and install updates as soon + as your other operating system distributions publish updates for + BootHole vulnerability. + + * Install package on Secureboot UEFI enabled system + * Reboot + * Observe that it still reboots [Regression Potential] - * Installing this package even once will update DBX variable in the + * Installing this package even once will update DBX variable in the UEFI firmware and will prevent booting: - - All Ubuntu, Debian, RHEL, Fedora, OpenSUSE, SUSE, Oracle Linux milestones / media released before August 2020 - - Certain version of Kaspersky Labs UEFI protect software - - Certain version of HPE Inc ProLiant automatic OS provisioning + - All Ubuntu, Debian, RHEL, Fedora, OpenSUSE, SUSE, Oracle Linux milestones / media released before August 2020 + - Certain version of Kaspersky Labs UEFI protect software + - Certain version of HPE Inc ProLiant automatic OS provisioning As they are all vulnerable to the BootHole vunlerability. For example, one will have to use 16.04.7 LTS, 18.04.5 LTS, 20.04.1 LTS installer media if they want to reinstall. If any dual boot configurations are failing to boot, one must navigated to UEFI BIOS settings and either reset DBX variables to stock values, or disable secureboot. Upgrade any systems that are now prohibited to boot. And then re-enable secureboot & reinstall secureboot-db package to reapply dbx updates. Please note simple downgrade of secureboot-db package will not achieve anything, as downgrading the package does not revert the firmware changes. [Other Info] - - * For more inforamtion please see https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/GRUB2SecureBootBypass + + * For more inforamtion please see + https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/GRUB2SecureBootBypass -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890835 Title: secureboot-db 2020 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/secureboot-db/+bug/1890835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890835] Re: secureboot-db 2020 update
This bug was fixed in the package secureboot-db - 1.6 --- secureboot-db (1.6) groovy; urgency=medium * Ship MS 2020 split arch dbx updates. LP: #1890835 * Add arm64 architecture. -- Dimitri John Ledkov Fri, 24 Jul 2020 00:34:57 +0100 ** Changed in: secureboot-db (Ubuntu Groovy) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890835 Title: secureboot-db 2020 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/secureboot-db/+bug/1890835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890835] Re: secureboot-db 2020 update
** Description changed: secureboot-db 2020 update Expecting long period in -proposed. - Expecting slow phasing in -updates. + Test to ensure certified laptops are not bricked before publishing to + updates. - One series at the time. + Expecting slow phasing in -updates, at 4% a day, 25 days in total. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890835 Title: secureboot-db 2020 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/secureboot-db/+bug/1890835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890835] Re: secureboot-db 2020 update
** Description changed: secureboot-db 2020 update + + Expecting long period in -proposed. + + Expecting slow phasing in -updates. + + One series at the time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890835 Title: secureboot-db 2020 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/secureboot-db/+bug/1890835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890835] Re: secureboot-db 2020 update
** Also affects: secureboot-db (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: secureboot-db (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: secureboot-db (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: secureboot-db (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: secureboot-db (Ubuntu Focal) Importance: Undecided Status: New ** Tags added: block-proposed-bionic block-proposed-focal block- proposed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890835 Title: secureboot-db 2020 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/secureboot-db/+bug/1890835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
