Skip to content

_internal/trust: Fix bug in rekor key lookup #1350

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 11, 2025

Conversation

jku
Copy link
Member

@jku jku commented Apr 11, 2025

Rekor keyring can (and in future will) have multiple keys: logs not only get sharded but once rekor-tiles is integrated in the public good instance, there will be two writable logs for a while.

As far as I can tell all calling code is already capable of handling the keyring.

Fixes #1349

Rekor keyring can (and in future will) have multiple keys:
logs not only get sharded but once rekor-tiles is integrated in the
public good instance, there will be two writable logs for a while.

As far as I can tell all calling code is already capable of handling
the keyring.

Signed-off-by: Jussi Kukkonen <jkukkonen@google.com>
woodruffw
woodruffw previously approved these changes Apr 11, 2025
Copy link
Member

@woodruffw woodruffw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@woodruffw
Copy link
Member

@jku actually, could you add a small CHANGELOG entry too? I imagine users of older versions might hit this once Sigstore shards and a CL entry will point them in the right direction.

Signed-off-by: Jussi Kukkonen <jkukkonen@google.com>
@jku jku merged commit 3418024 into sigstore:main Apr 11, 2025
23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

multiple rekor keys should be allowed
2 participants