Use tuf to init signer and verifier #492
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
loosebazooka
force-pushed
the
tuf-in-keyless-workflows
branch
from
3e3d622 to
6f937e7
Compare
Signed-off-by: Appu Goundan <[email protected]>
loosebazooka
force-pushed
the
tuf-in-keyless-workflows
branch
from
6f937e7 to
34dcb33
Compare
vlsi
approved these changes
Sep 8, 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.
This does not the solve the problem of TUF going out of date while a long long signing operation is in progressr. I believe we'd have to work that into something similar to the certificate caching mechanism.
~~ needs #493 ~~
here's the diff with the original signer and verifier: https://github.com/sigstore/sigstore-java/compare/diffbase-for-keyless2..tuf-in-keyless-workflows