This preloader is simpler to use as it works with unsigned efi binaries as well. Shim does not allow that - at least that was what i noticed. Why shim is allowed to add a key (i.e. MOK.cer) and this loader not is a bit weird. The error that MS most likely found is there with hashes as well - i see no way to reset those when they have been added. Try yourself you have got a board with Secure Boot - preferred do a backup of your firmware before (you can use flashrom for some boards).


Reply With Quote
You can enroll any hash/key you want. With phyiscal access you usally could disable Secure Boot anyway, so you lose nothing. It is just simpler for noobs to boot Linux without changing firmware settings when the loader is signed. Some loaders enforce signed kernels and the kernel itself could be patched as well to disable loading of unsigned kernel modules. The problem there is that you can just exchange the bootloader. It would be even more fun when somebody finds a way to modify the key db inside Linux.

