Yes, it's absolutely possible to recreate the environment for testing
this without MAAS -- there's nothing all that special to it,
chainloading *any* image should work and maintain a Secure Boot-verified
chain provided all the links in the chain validate images.
This looks to be pretty clearly a bug in chainloader's validation of
images, it used to work, but only because it wasn't actually verifying
much of it in the first place.
** Changed in: grub2 (Ubuntu)
Status: New => In Progress
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711203
Title:
Deployments fail when Secure Boot enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1711203/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
