Public bug reported:

[Impact]

The Ubuntu signing box is currently 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 Focal's sbsign
    sbsign --key db.key --cert db.crt test.efi
  - check the signature with Jammy's sbverify
    sbverify --cert db.crt test.efi.signed
  - check the signature with Focal'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]

* A separate SRU #1964510 is requested for Bionic. We need this SRU so
that we don't loose functionality in case of an upgrade from Bionic to
Focal.

** Affects: sbsigntool (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: fr-2104 riscv64

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

Title:
  [SRU] enable signing riscv64 binaries in focal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sbsigntool/+bug/1964519/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to