-
Notifications
You must be signed in to change notification settings - Fork 31
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
[Proposal] Require inclusion proofs #82
Comments
|
haydentherapper
added a commit
to haydentherapper/protobuf-specs
that referenced
this issue
Jun 30, 2023
The log always generates inclusion proofs, so we will make it a requirement that clients verify the proof. Promises will be deprecated over time, but for now, we'll make them optional. Fixes sigstore#82 Ref sigstore/rekor#1566 Signed-off-by: Hayden Blauzvern <hblauzvern@google.com>
kommendorkapten
pushed a commit
that referenced
this issue
Jul 3, 2023
* Require inclusion proofs, make promises optional The log always generates inclusion proofs, so we will make it a requirement that clients verify the proof. Promises will be deprecated over time, but for now, we'll make them optional. Fixes #82 Ref sigstore/rekor#1566 Signed-off-by: Hayden Blauzvern <hblauzvern@google.com> * Bump version Signed-off-by: Hayden Blauzvern <hblauzvern@google.com> * Update client verification requirements for promises Signed-off-by: Hayden Blauzvern <hblauzvern@google.com> --------- Signed-off-by: Hayden Blauzvern <hblauzvern@google.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As discussed in sigstore/rekor#1566, I am proposing that inclusion proofs in bundles become mandatory. There are no server-side changes, as these are already returned.
Here's a table of the current support for inclusion proofs per client, and how they support verifying proofs (included SETs to be thorough).
@bdehamer @woodruffw @loosebazooka @znewman01 Please let me know if anything is inaccurate or help fill in the question marks.
The text was updated successfully, but these errors were encountered: