shim-systemd: Install & update the Mok Management executable on the ESP #254
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
The Mok Management EFI executable (generally mmx64.efi) is needed in a few cases (when secure boot is enabled): - When using a third-party shim requiring you to enroll your own cert on first boot - When using a custom kernel or bootloader allowing the user the enroll the hash of it in order to boot According to the layout comment on the top of the file this should already be expected to be on the ESP, fix that.
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.
The Mok Management EFI executable (generally mmx64.efi) is needed in a few cases (when secure boot is enabled):
According to the layout comment on the top of the file this should already be expected to be on the ESP, fix that.