Jump to content
30960 posts in this topic

Recommended Posts

I updated the release 5172 without changing the release number. It is the same in functionality but compiled by GCC.

Also there are new icons from Chris1111. Thanks!

New books are here https://github.com/CloverHackyColor/CloverBootloader/releases/download/5172/Clover_Of_Khaki_Color_5172-en.pdf

  • Like 4
  • Thanks 3
  • 2 weeks later...

@Slice

Greetings

Tried to enable secure boot

Compiled Clover 🍀 with

./buildme "" ci -D ENABLE_SECURE_BOOT=1

Clover efi and all other efi from drivers and tools was signed.. 

sbsign --key db.key --cert db.crt --output signed_bootloader.efi original_bootloader.efi

x509 certificate endabled in bios rom

Mac partition are displayed/loaded in clover only with apfs.efi

All that without success

What should I edit in clover plist?

I'm lost

  • Like 1

@MICKHAEL

 

This is for Opencore; I'm not sure if it also applies to Clover. You can try it and let me know the result.

 

 

As you can see, the idea is that, instead of digitally signing the binaries in the EFI folder, you enroll all the .efi files in the UEFI database secure variable, which is a list of allowed signatures, so that UEFI Secure Boot accepts these .efi files as safe. You don't modify or sign the .efi files; you just tell the firmware to consider them safe to boot even if UEFI Secure Boot is enabled.

 

To do this, you have to restore the default keys in UEFI Secure Boot from the BIOS menu to remove anything you've added to them. Then, in the Enroll EFI Image menu of UEFI Secure Boot, add all the .efi files one by one. If this Enroll EFI Image menu (or something similar) doesn't exist, then this method won't work for you.

 

If you can try it, please let me know the result.

 

The worst that can happen is that this method doesn't work either, in which case you have to go back to Reset Default Keys in UEFI Secure Boot.

  • Like 4
×
×
  • Create New...