Skip to content

Add function for determining key_details #1456

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 9 commits into from
Jul 16, 2025

Conversation

ramonpetgrave64
Copy link
Contributor

@ramonpetgrave64 ramonpetgrave64 commented Jun 20, 2025

Summary

Client support for Rekor V2: sigstore-python #289

Partially addresses #1439

Inspired by https://github.com/sigstore/sigstore-python/pull/1432/files#diff-0287921ae266ddac61ace4f5d2ee5fa8e74495f6e3a7c231d3715a31679690b1R622-R651

Adds a function for determining the key_details of a certificate.

Note that this does not add direct support for signing with the various key types, but in the future will aid with sending requests to Rekor and verifying Entry body contents.

Release Note

  • Added a function for determining the key_details of a certificate`.

Documentation

@ramonpetgrave64 ramonpetgrave64 marked this pull request as ready for review June 20, 2025 20:36
Signed-off-by: Ramon Petgrave <[email protected]>
Copy link
Member

@jku jku left a comment

Choose a reason for hiding this comment

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

The actual method looks pretty good (although maybe it could live in sigstore/_utils.py like other random methods like this).

Addresses #1439

This is not true since this only modifies the signing code (I assume the plan was to extend this to support verification as well later on) .

  • I think we can re-use the code for signing and verification like it looks like you planned but it's worth noting that
    1. The signing code does not strictly speaking need this support (since there keytype is hard coded anyway and there's no plans to make that configurable at the moment)
    2. this re-use saves 7 lines of code
    3. the requirements for signing & verification might end up different: maybe we want to support the "not recommended" algorithms for verification but not for signing
  • let's at least wait until #1432 so we can plug this into the verification code where it will be actually useful

Copy link
Member

@jku jku left a comment

Choose a reason for hiding this comment

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

I'm going to approve this and handle #1439 in another PR using this

@jku
Copy link
Member

jku commented Jul 16, 2025

/gcbrun

@jku jku merged commit a18d758 into sigstore:main Jul 16, 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.

2 participants