This repository has been archived by the owner on Apr 22, 2024. It is now read-only.
fix: use correct secureboot AKMOD_PRIVKEY_20230518 #31
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 very short-lived key AKMOD_PRIVKEY_20230517 was accidentally included here instead of the proper one. This correct key is the one we actually use to sign akmods (and also is used by bazzite to sign the whole kernel). So we definitely need this to be correct.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 very short-lived key AKMOD_PRIVKEY_20230517 was accidentally included here instead of the proper AKMOD_PRIVKEY_20230518 key.
This correct key is the one we actually use to sign akmods (and also is used by bazzite to sign the whole kernel). So we definitely need this to be correct.