Re:Booting a Self-signed Linux Kernel
by richardwhiuk on Tuesday September 03, 2013 @04:58AM
(#6319836)
You have to disable the Secure Boot protection before you can run KeyTool - from the article:
Traverse the BIOS settings and find the place where UEFI boot mode is specified, and turn it the “Secure Boot” option OFF."
Why does KeyTool even run on a locked-down-by-MS machine? Have they signed it as part of the Linux Foundation bootloader? Why would they do such a thing? I don't mean for protecting-the-monopoly-reasons, but for straight security reasons as this clearly circumvents anything they were trying to accomplish.
I seem to be missing a piece of information here.