Repository navigation
docs(readme): cosign v3, or v2.6 with --new-bundle-format, to verify the images - #501
Merged
Merged
Conversation
…the images (#488) The lea and lea-proxy images are signed in the Sigstore bundle format (cosign v3 in the release workflow). cosign v2 answers 'no signatures found' unless --new-bundle-format is given, and the flag only finds the bundle from v2.6.0 on (checked by hand on 0.17.2 with v2.5.0 to v2.6.1 and v3.1.4). Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
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.
Closes #488
What changed
README.md, "Verify a release": the by-hand paragraph now says that the images are signed in the Sigstore bundle format, that verifying them needs cosign v3 or later, or cosign v2.6 or later with--new-bundle-format, and that cosign v2 without the flag answersno signatures foundalthough the image is signed. The example gains a comment line with the exact flag for cosign v2. Thecosign verifycommand itself is unchanged: it succeeds as written with cosign v3.One difference from the ticket
The ticket says "cosign v2.5+ with
--new-bundle-format". By hand, v2.5.0, v2.5.1, v2.5.2 and v2.5.3 accept the flag but still answerno signatures foundon both images; v2.6.0 and v2.6.1 succeed. The README therefore says v2.6 or later.no signatures foundno signatures found--new-bundle-format--new-bundle-format--new-bundle-formatno signatures foundno signatures foundHow it was verified
cosign v3.1.4 is the one on the
PATH(Homebrew); each v2 binary iscosign-linux-amd64from its Sigstore GitHub release, checked against that release'scosign_checksums.txt. Outputs (the JSON line is cut at 600 characters):README only, no code touched, so no test suite was run.
🤖 Generated with Claude Code