Thanks for the test. It looks like we're getting farther. The error
messages here indicate that the \EFI\ubuntu\grubx64.efi on this disk is not
signed with the Canonical key. In fact, it's not signed by any key ("Empty
security header"). Can you double-check your image, and make sure to use
the unmodified grubx64.efi from the standard Ubuntu image? The *only*
change from the standard Ubuntu image at this point should be the copy of
shim.
Hi Franz,
On Wed, Jul 17, 2013 at 06:53:59AM -0000, Franz Hsieh wrote:
> We have run LockDown.efi and then enable secure boot.
> The errors are attached in the picture.
> ** Attachment added: "17 下午2:50:10.jpeg" /bugs.launchpad .net/ubuntu/ +source/ shim/+bug/ 1187233/ +attachment/ 3739636/ +files/ 17%20%E4% B8%8B%E5% 8D%882% 3A50%3A10. jpeg
> https:/
Thanks for the test. It looks like we're getting farther. The error grubx64. efi on this disk is not
messages here indicate that the \EFI\ubuntu\
signed with the Canonical key. In fact, it's not signed by any key ("Empty
security header"). Can you double-check your image, and make sure to use
the unmodified grubx64.efi from the standard Ubuntu image? The *only*
change from the standard Ubuntu image at this point should be the copy of
shim.