Skip to content
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

Fixed typo, removed mention enroll-keys enables Secure Boot automatic… #270

Merged
merged 1 commit into from
Dec 23, 2023

Conversation

tblancher
Copy link
Contributor

…ally

Huh, GitHub has a less than 80 character limit to commit messages.

Per https://wiki.archlinux.org/title/Talk:Unified_Extensible_Firmware_Interface/Secure_Boot#Enrolling_keys_with_sbctl_enables_Secure_Boot, enroll-keys does NOT enable Secure Boot. It still has to be done manually through the UEFI BIOS firmware settings.

@Foxboron
Copy link
Owner

Thanks!

@tblancher tblancher temporarily deployed to Build, sign, release binaries December 18, 2023 07:55 — with GitHub Actions Inactive
@tblancher tblancher temporarily deployed to Build, sign, release binaries December 18, 2023 07:55 — with GitHub Actions Inactive
@tblancher tblancher temporarily deployed to Build, sign, release binaries December 18, 2023 07:55 — with GitHub Actions Inactive
@Foxboron Foxboron merged commit 9e8bd16 into Foxboron:master Dec 23, 2023
5 of 6 checks passed
@tblancher
Copy link
Contributor Author

@Foxboron When I finally got down to trying this, my Lenovo X1 Carbon, 11th gen does NOT offer a way to enable Secure Boot in the UEFI BIOS Security menu within its settings. I can disable Secure Boot, enter Setup Mode from the UEFI settings, but not enable it; it looks like that enabling it has to come from the OS.

The only way I was able to enable Secure Boot was with sbctl enroll-keys --microsoft. Maybe it depends on the system, and its compatibility with sbctl?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants