Conversation
Signed-off-by: Andrew Pan <andrew.pan@trailofbits.com>
Contributor
Author
|
I'll need some help with why the tests are failing, not sure if we just need to bump some Ruby deps? |
Member
|
I'm about to push up a pr that bumps the conformance suite and adds rekorv2 support |
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
3 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.
sigstore-ruby accepted a Sigstore bundle whose Rekor v1 transparency log entry contains an inclusion proof and checkpoint, but did not contain a Signed Entry Timestamp (SET). The verifier then used the associated integratedTime as signing-time evidence even though that timestamp was not signed by Rekor.