[Bug 1964510] Please test proposed package
Steve Langasek
1964510 at bugs.launchpad.net
Tue May 3 11:18:50 UTC 2022
Hello Heinrich, or anyone else affected,
Accepted sbsigntool into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/sbsigntool/0.9.2-2ubuntu1~18.04.2
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.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to sbsigntool in Ubuntu.
https://bugs.launchpad.net/bugs/1964510
Title:
[SRU] enable signing riscv64 binaries in bionic
Status in sbsigntool package in Ubuntu:
Fix Released
Status in sbsigntool source package in Bionic:
Fix Committed
Status in sbsigntool source package in Focal:
Fix Committed
Bug description:
[Impact]
The Ubuntu signing box is running Ubuntu Bionic. The riscv64
architecture is expanding. We expect development boards using EDK II
to appear in 2022. We should be able to support secure boot then.
A patch for enabling this has been accepted upstream:
https://git.kernel.org/pub/scm/linux/kernel/git/jejb/sbsigntools.git/commit/?h=next&id=25af2eb5e39b5d54703d4489182a6b9d0af58b76
[Test Plan]
* Signatures produced by sbsign in bionic, must be verifiable with
sbverify from jammy.
* Test instructions:
- create as new certificate RSA2048) for signing EFI binaries
openssl req -x509 -sha256 -newkey rsa:2048 -subj /CN=TEST_$*/ \
-keyout db.key -out db.crt -nodes -days 3650
- sign amd64, arm64 and riscv64 EFI binaries with Bionic's sbsign
sbsign --key db.key --cert db.crt test.efi
- check the signature with Jammy's sbverify
- check the signature with Bionics's sbverify
* Testing should be executed before landing the update.
[Where problems could occur]
* The upstream patch is trivial and should have no effect on any non-
riscv64 architecture. It only changes the architecture test that is
made before signing.
* With the test procedure above we ensure that we still can sign on
the same architectures as before.
[Other Info]
* The Focal task is so that we don't loose functionality in case of an
upgrade from Bionic to Focal.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sbsigntool/+bug/1964510/+subscriptions
More information about the foundations-bugs
mailing list