Skip to content

Conversation

@jku
Copy link

@jku jku commented Oct 21, 2025

Sigstore public good instance is transitioning to Rekor v2 transparency log: v2 no longer includes integrated time in the log entries so external timestamps are needed.

The companion PR to this is pypi/pypi-attestations#143. There is an overall tracking issue in pypi/pypi-attestations#147

This is definitely still draft:

  • I've not gone through the document to ensure there aren't other changes that are required
  • I'm not sure if the attestation format needs a version change for this or not

Sigstore public good instance is transitioning to Rekor v2 transparency
log: This log no longer includes integrated time in the log entries and
external timestamps are then needed.
@webknjaz webknjaz requested review from Copilot and woodruffw October 21, 2025 11:15
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR adds optional RFC3161 timestamp support to the attestation format, enabling compatibility with Sigstore's Rekor v2 transparency log which no longer includes integrated timestamps in log entries.

Key Changes

  • Added optional timestamps field to verification material for storing external RFC3161 timestamps
  • Updated verification requirements to clarify that inclusion time can come from either integrated timestamps or external RFC3161 timestamps
Comments suppressed due to low confidence (1)

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

jku added 2 commits October 29, 2025 15:41
I'm trying to not include too much detail here as the doc already
states that entry verification depends on policy... but dsse 0.0.1
is the rekor v1 entry type used in the attestations so maybe this
works?
@jku
Copy link
Author

jku commented Oct 29, 2025

I'd like to get some advice on how to handle the fact that I'm adding a new field to the attestation:

  • Are the only potential incompatibilities within pypi-attestations project or should I look elsewhere too?
  • The attestation has a version (1), should that be bumped? the pypi-attestations code does not need it but at least I could then mention in a comment that version 1 did not have the timestamps field...

@woodruffw
Copy link
Member

  • Are the only potential incompatibilities within pypi-attestations project or should I look elsewhere too?

That's the main place, yeah 🙂

  • The attestation has a version (1), should that be bumped? the pypi-attestations code does not need it but at least I could then mention in a comment that version 1 did not have the timestamps field...

Yeah, I think we probably should bump it -- it's technically a semantic change to verification.

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