Comment 12 for bug 1865515
Revision history for this message
| Steve Langasek (vorlon) wrote Re: [Bug 1865515] Re: Chainbooting from grub over the network to local shim breaks chain of trust | #12 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
On Tue, May 19, 2020 at 08:59:46PM -0000, Lee Trager wrote:
> Based on the MAAS logs the halt happens after the remote shim, grub, and
> grub.cfg have been loaded. I didn't see anything in the console to show
> grub running but it may have been cleared before I could see it.
> Console output:
> Booting local disk...
> Failed to open \efi\boot\
> Failed to load image \efi\boot\
> start_image() returned Not Found
> Bootloader has not verified loaded image.
> System is compromised. halting.
Doesn't this output show that it has successfully chained to the local shim,
since it's shim that is loading \efi\boot\
from shim?
What I don't currently understand is why this should behave any differently
with or without SecureBoot enabled; that will need digging into. But the
specific error "Not found" certainly implies there is a difference in the
path resolution when secureboot is on.