-
Notifications
You must be signed in to change notification settings - Fork 232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add guide to UEFI Secure Boot #139
base: master
Are you sure you want to change the base?
Conversation
also #14 exist but its been a draft for over 4 years so idk |
@some100 There is an easier method to enroll efi images into the firmware, in my opinion not only it is much simpler but it also has much less risk of damaging the BIOS (with the classic method, sometimes you can get a bricked BIOS and have to recover it from a backup BIOS). You can read about it on my GitHub: In the part explaining how to insert secure variables into the firmware I miss modern BIOS images from American Megatrends International (AMI), which are present on many Gigabyte and Asus boards today. It's not a big deal but AMI Aptio V images are not the usual ones these days. Finally, the merging of OpenCore Vault with UEFI Secure Boot is poorly explained in Dortania's guide. Maybe it's useful to add a comment on how to do it. You can see my proposal here (I proposed this a while ago in the bug tracker but it has never been implemented): Anyway, I appreciate the work you've done, completed with instructions for Linux working on shim as well. |
Included comments on Vaulting with Secure Boot. Thanks for the suggestion |
adds a guide to uefi secure boot
includes using shim with opencore