Always include vendor keys in status output #205
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Do not hide the "vendor keys" line if there are no vendor keys; instead indicate explicitly that no vendor keys are present.
I found this behaviour a bit confusing when setting up secure boot; it took me a while to realize that the MS keys were indeed not installed, because a flag in the firmware UI suggested otherwise, and I assumed sbctl was misbehaving.
Given that the absence of vendor keys can cause a lot of trouble depending on the hardware, I also think it's better to indicate their absence explicitly.