feat: use sigstore signing#974
Open
valoq wants to merge 2 commits intoouch-org:mainfrom
Open
Conversation
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
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.
This PR adds automated signature creation using sigstore.
Sigstore is a modern approach to signing source code and binary releases that does not require developers to maintain and secure private signature keys and simplify the signature process. Effectively signatures are done using short lived signing keys bound to the authentication process. Validation is done through a transparency log approach. this means all release signatures are logged in the public transparency log, allowing everyone to verify that the signature was authenticated in github. It will also list all signatures created, so even if the repo were to be compromised, all new signatures would be visible and cannot be hidden.
The advantages: