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

Unenroll keys #248

Open
BRTPOB opened this issue Sep 30, 2023 · 4 comments
Open

Unenroll keys #248

BRTPOB opened this issue Sep 30, 2023 · 4 comments

Comments

@BRTPOB
Copy link

BRTPOB commented Sep 30, 2023

I was attempting to get Secure Boot setup on my Surface Book 2 and I seem to have skipped some steps, so I've got sbctl installed but I can't actually get it working as it should. Looking at the help and man pages, there's nothing that explains how to properly unenroll/remove the keys that were generated so that I can start from scratch.

Is there an option/ability to do so, and if so, what are the commands needed for that?

Also feels like this would be good to be documented somewhere, as I'm sure others have run into this as well.

@Liassica
Copy link

The process for unenrolling the sbctl-enrolled keys is the same as removing the manufacturer keys (or any other secure boot keys). See steps 1-5 of the example workflow.

As for the keys themselves, I would figure deleting the directory they were installed to (/etc/secureboot by default) would be sufficient, although you could probably reuse them.

@IPlayZed
Copy link

@Foxboron Is there the way to query the firmware to reset all keys to vendor provided one programatically from userspace? I see that in the documentation, there is the reset subcommand, but it only resets the PK, not the KEK, DB, DBX.

@Foxboron
Copy link
Owner

You misunderstand what the reset commands does. It removes the PK to out you into setup mode. You can freely run rotate-keys or enroll-keys.

You can't only enroll vendor provided ones, that isn't the job of sbctl. Use the BIOS menu for that.

@IPlayZed
Copy link

Than this issue could be closed to not clutter the actual ones.

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

No branches or pull requests

4 participants