> shim-signed is won't fix.
No, it absolutely is not.
The behavior of shim is WRONG and MUST be fixed; we've previously
idenitfied that this affects not only cross-distro chainloading, it also
impacts chainloading from the removable disk shim to
\EFI\ubuntu\shimx64.efi via fallback.efi on non-TPM-enabled hardware.
And per Julian, there has been acknowledgement from upstream that the
behavior here needs to be fixed.
** Changed in: shim-signed (Ubuntu)
Status: Won't Fix => Triaged
** Changed in: shim-signed (Ubuntu Focal)
Status: Won't Fix => Triaged
** Changed in: shim-signed (Ubuntu Groovy)
Status: Won't Fix => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865515
Title:
Chainbooting from grub over the network to local shim breaks chain of
trust
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1865515/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
