Sign release checksums with Cosign - #914
Open
scop wants to merge 1 commit into
Open
Conversation
Refs - https://www.sigstore.dev - https://docs.sigstore.dev/cosign/signing/overview/ - https://github.com/sigstore/cosign - https://goreleaser.com/customization/sign/sign/#signing-with-cosign This yields a checksums.txt.sigstore.json in release assets, which can be used to verify the checksums file and thus transitively files listed in it. This can be done manually using cosign, and software such as aqua and mise can do it automatically on install. Note: with this, one likely wants to use --skip=sign if running goreleaser release --snapshot to test (other) things locally.
Up to standards ✅🟢 Issues
|
Owner
|
Will create an issue for this and do some research, I really don't know much about sigstore or signature signing yet so its hard to know if this is helpful or not. Sorry for the delay. |
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
2 participants
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.
Refs
This yields a checksums.txt.sigstore.json in release assets, which can be used to verify the checksums file and thus transitively files listed in it. This can be done manually using cosign, and software such as aqua and mise can do it automatically on install.
Closes #NNNCheck the following
Additional context
Note: with this, one likely wants to use --skip=sign if running goreleaser release --snapshot to test (other) things locally.
Caveat: untested, but have set this up for multiple projects, one recent sample at daveshanley/vacuum#927