There is no other way to deploy with secureboot, without modifying the deployed OS shim.
Thus either we fix above two bugs as well, or those targets will not have secureboot and continue to use chainloading. Requirements for secureboot are: * create valid uefi boot entries * do not delete them * use exit 1 to boot local disk -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
