[Bug 1087843] Please test proposed package

Adam Conrad adconrad at 0c3.net
Mon Feb 4 18:28:34 UTC 2013


Hello Jamie, or anyone else affected,

Accepted grub2-signed into quantal-proposed. The package will build now
and be available at
http://launchpad.net/ubuntu/+source/grub2-signed/1.9ubuntu0.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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  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!

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

Title:
  [MIR] secureboot-db

Status in “grub2-signed” package in Ubuntu:
  New
Status in “secureboot-db” package in Ubuntu:
  Fix Released
Status in “shim-signed” package in Ubuntu:
  New
Status in “grub2-signed” source package in Precise:
  Fix Committed
Status in “secureboot-db” source package in Precise:
  Fix Released
Status in “shim-signed” source package in Precise:
  New
Status in “grub2-signed” source package in Quantal:
  Fix Committed
Status in “secureboot-db” source package in Quantal:
  Fix Released
Status in “shim-signed” source package in Quantal:
  New
Status in “grub2-signed” source package in Raring:
  New
Status in “secureboot-db” source package in Raring:
  Fix Released
Status in “shim-signed” source package in Raring:
  New

Bug description:
  Availability: The package is in universe in 13.04 (pending bug
  #1081700)

  Rationale: This package is provided as part of Ubuntu's secure boot
  strategy and will also be backported to 12.04 LTS and 12.10 as part of
  https://blueprints.launchpad.net/ubuntu/+spec/foundations-r-secure-
  boot.

  Security: The package is new and has no security history. It is also
  simple and only ships data and runs sbkeysync in postinstall.

  Quality assurance: there is no special configuration. Install the
  package and updates to DB and DBX are automatically performed in
  postinst via sbkeysync. There are no debconf questions or outstanding
  bugs. The package is for Ubuntu only, which is why it uses native
  packaging. There is no testsuite as there is no code to test. The
  package is lintian clean. The package ships a README.source which
  details how to add new signed updates to the package and testing
  procedures are documented and given to Foundations, QA, Security and
  PES.

  UI standards: N/A

  Dependencies: the package has a binary dependency on sbsigntool, which
  is already in main.

  Standards compliance: The package meets FHS and Debian Policy
  standards.

  Maintenance: The package will be maintained by Ubuntu Foundations and
  Ubuntu Security.

  Background information: In order to properly support secure boot, we
  need a method to update the DB and DBX key databases to support key
  rotation and blacklisting.

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




More information about the foundations-bugs mailing list