-
Notifications
You must be signed in to change notification settings - Fork 49
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
Support generating and verifying with "Sigstore" bundles #251
Comments
Marking this blocked on sigstore/cosign#2131 |
The sigstore bundle spec is being developed in |
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 |
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 |
I'm going to prepare a PR for verifying bundles. |
Done as of #478! |
Not a big deal, but should the subtask
in the issue description be checked and linked to #478? |
Yes, thanks @edgarrmondragon! |
There are currently (at least) 3 different things called "bundles" in the Sigstore ecosystem:
cosign --bundle
emits. These contain a Rekor entry, plus checksum, certificate, and signature needed to perform a normal verification step.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.
Subtasks:
sigstore sign
(Initial Sigstore bundle support #465)sigstore verify
subcommands (Support verifying Sigstore bundles #478)The text was updated successfully, but these errors were encountered: