sigstore-python
sigstore-python copied to clipboard
Support generating and verifying with "Sigstore" bundles
There are currently (at least) 3 different things called "bundles" in the Sigstore ecosystem:
- "cosign bundles", which
cosign --bundleemits. These contain a Rekor entry, plus checksum, certificate, and signature needed to perform a normal verification step. - "Rekor offline bundles", which contain just the Rekor entry and its SET. These need to be combined with separate inputs to perform a normal verification step.
- "sigstore bundles", which are currently being designed (https://github.com/sigstore/cosign/pull/2204). These will deprecate "cosign bundles" and perform the same function.
Once the "Sigstore bundle" format is stabilized, sigstore-python should both consume and emit it (by default, rather than emitting/loading separate files for each component).
This is a counterpart to #52 and #194, and will obviate/deprecate the work in #247 once finished.
Marking this blocked on https://github.com/sigstore/cosign/issues/2131
The sigstore bundle spec is being developed in sigstore/protobuf-specs; tracking https://github.com/sigstore/protobuf-specs/issues/6
nothing against protobufs as such but it'll likely be yet another dependency just to read a single config file :(
nothing against protobufs as such but it'll likely be yet another dependency just to read a single config file :(
Yeah, this isn't ideal (but also not the end of the world). My plan here was to look into generating a separate Python package from the protobuf specs, something like sigstore-protos or sigstore-models, so that we can avoid a direct protobuf dependency.
Or we could have the repo that defines the specs generate/publish the protos package as well.
Bumping this to post-stable, since the Sigstore bundle format itself isn't fully stabilized.
Unblocking because a 0.1 release of the bundle format is now available; we should begin evaluating against it.
I'm going to prepare a PR for verifying bundles.
Done as of #478!
Not a big deal, but should the subtask
- [ ] Verify using Sigstore-style bundles with the
sigstore verifysubcommands
in the issue description be checked and linked to https://github.com/sigstore/sigstore-python/pull/478?
Yes, thanks @edgarrmondragon!