Repository navigation
fulciotest: a test Sigstore whose certificates carry Fulcio's extensions - #38
Merged
Merged
Conversation
A verifier of a reusable builder must pin the source repository, since any repository may call a public reusable workflow and be issued its SAN. Its tests need certificates that say a source repository, which sigstore-go's VirtualSigstore does not mint. fulciotest keeps the VirtualSigstore's Rekor, CT log and TSA and brings its own Fulcio CA: SignAtTime (a hashedrekord entry, as cosign sign-blob's) and AttestAtTime (DSSE, with or without the inclusion proof), each for a URI SAN and a certificate.Extensions. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <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
1 participant
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.
After S5 a verifier must pin the source repository (any repository may call a public reusable builder and be issued its SAN), and its tests need certificates that carry one. sigstore-go's VirtualSigstore mints a leaf with only the issuer.
fulciotest.New()keeps the VirtualSigstore's Rekor, CT log and TSA, and brings its own Fulcio CA (FulcioCertificateAuthoritiesoverridden):SignAtTime(san, ext, artifact, at): a message signature with a hashedrekord entry and inclusion promise, ascosign sign-blobmakes;AttestAtTime(san, ext, body, at, proof): DSSE, with or without the inclusion proof;--certificate-github-workflow-repositoryreads.The test pins SourceRepositoryURI and BuildConfigURI with sigstore-go's own verifier: the own repository passes, another repository with the builder's SAN fails, and so does a certificate that names no source (planted: without the pin both of those pass). It also checks the SAN, a non-URI SAN, a missing issuer, and signing after Fulcio's validity.
Also: grpc v1.83.1 and x/net v0.60.0. rekor brings them into the graph, and vulngate flags called vulnerabilities in the old ones (GO-2026-6348, -6603, -6611, -6612, -6617).
task lint,task mutate(0 survived).🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need.