[Fleet] Enable package signature verification feature #137239
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
botelastic
bot
added
the
Team:Fleet
|
Pinging @elastic/fleet (Team:Fleet) |
hop-dev
added
release_note:feature
jen-huang
approved these changes
Jul 26, 2022
💚 Build Succeeded
Metrics [docs]
To update your PR or re-run it, just comment with: cc @hop-dev |
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.
Summary
Closes #133822
Enable the package signature verification feature by default.
Package signature verification allows users to better trust the contents of packages. When package registry v2 is launched all packages will be accompanied by a .sig file generated by elastic. Enabling the feature flag means that all packages with a signature available will have the package zip checked against this signature.
If a package fails verification then the user will be alerted in the UI.
If a package does not have a signature, the package will be marked as having an "unknown" verification status, which currently does not show in the UI. This prevents already installed packages from showing as unverified.