[Bug 1890835] Please test proposed package

[Łukasz Zemczak]

Hello Dimitri, or anyone else affected,

Accepted secureboot-db into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/secureboot-
db/1.4.1~ubuntu0.16.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-
xenial to verification-done-xenial. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-xenial. 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.

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

Title:
  secureboot-db 2020 update

Status in secureboot-db package in Ubuntu:
  Fix Released
Status in secureboot-db source package in Trusty:
  New
Status in secureboot-db source package in Xenial:
  Fix Committed
Status in secureboot-db source package in Bionic:
  Fix Committed
Status in secureboot-db source package in Focal:
  Fix Committed
Status in secureboot-db source package in Groovy:
  Fix Released

Bug description:
  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
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/secureboot-db/+bug/1890835/+subscriptions