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

[Ivan Kapelyukhin]

Public bug reported:

[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 create 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

** Affects: livecd-rootfs (Ubuntu)
     Importance: Undecided
         Status: New

-- 
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:
  New

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 create 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