Update SET docs for timestamping #100
Merged
Conversation
This file contains 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
woodruffw
reviewed
Jul 26, 2023
SETs serve two purposes: The promise of inclusion, and a signed timestamp from Rekor. We've moved towards requiring inclusion proofs, but SETs are still needed if no TSA timestamp is provided. This doc update clarifies that. Signed-off-by: Hayden Blauzvern <hblauzvern@google.com>
haydentherapper
force-pushed
the
doc-update
branch
from
8c42b38
to
04b784c
Compare
woodruffw
reviewed
Jul 26, 2023
Co-authored-by: William Woodruff <william@yossarian.net> Signed-off-by: Hayden B <hblauzvern@google.com>
woodruffw
approved these changes
Jul 26, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
SETs serve two purposes: The promise of inclusion, and a signed
timestamp from Rekor. We've moved towards requiring inclusion proofs,
but SETs are still needed if no TSA timestamp is provided. This doc
update clarifies that.
Signed-off-by: Hayden Blauzvern hblauzvern@google.com
Summary
Release Note
Documentation