Repository navigation
The instructions say which key signed the build they ship with - #156
Merged
Merged
Conversation
…ease's, made offline and enrolled once, or a development build's, made by that build and its own, so the same page is true of a 0.x pre-release and of a production release
This file contains hidden or 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
1 participant
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.
docs/user-guide.md is shipped as INSTRUCTIONS.md with every release. Its Secure Boot paragraph and its known-limitations list said the kernel is signed with a developer key generated by the build, which is true of a 0.x pre-release and false of a production release. Both passages now say which key signs which kind of build, so the page is right for 1.0.0 without a release-day edit. Docs only.