I'm just wondering where Maas is getting the grubx64.efi from, I
assume/hope it's the grubnetx64.efi binary built by the grub package.
Because the bug might be in there.
Anyway, this should be enough to investigate further and sounds somewhat
familiar too
** Changed in: shim-signed (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: grub (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: shim-signed (Ubuntu)
Status: Confirmed => Triaged
** Changed in: grub (Ubuntu)
Status: Confirmed => 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
