[Bug 1980358] Re: ARM64 images don't boot when secureboot is enabled

[Utkarsh Gupta]

Marked the bug to reflect the status of each series. What about Impish?

** Also affects: livecd-rootfs (Ubuntu Impish)
   Importance: Undecided
       Status: New

** Also affects: livecd-rootfs (Ubuntu Bionic)
   Importance: Undecided
       Status: New

** Also affects: livecd-rootfs (Ubuntu Jammy)
   Importance: Undecided
       Status: New

** Also affects: livecd-rootfs (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Changed in: livecd-rootfs (Ubuntu)
       Status: New => Fix Released

** Changed in: livecd-rootfs (Ubuntu Jammy)
       Status: New => Fix Released

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

Title:
  ARM64 images don't boot when secureboot is enabled

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Bionic:
  New
Status in livecd-rootfs source package in Focal:
  New
Status in livecd-rootfs source package in Impish:
  New
Status in livecd-rootfs source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * ARM64 images fail to boot when secureboot is enabled, this is due to Focal and Bionic
     images having unsigned `shim` and `grub-efi-arm64`

  [Test Plan]

   * Build an ARM64 image and ensure that it boots when secureboot is
  enabled

  [Where problems could occur]

   * A lot of different derivative images inherit from `disk-image-uefi.binary`, this change
     has the potential to tamper with the arcane matters related to boot

  [Other Info]

   * This is a backport, images of Jammy and newer have had those
  changes since release

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1980358/+subscriptions