initialize cosign trust root after install#220
Open
crazy-max wants to merge 1 commit into
Open
Conversation
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 initializes Cosign's Sigstore trust root immediately after Cosign is installed.
Each existing Cosign install step now runs
cosign initializethrough the installed Cosign binary before later signing or verification commands run in that job.This takes a smaller workflow-level approach than docker/actions-toolkit#1125 and docker/actions-toolkit#1133, which tried to pin or thread an explicit trusted root path through
actions-toolkit. Those approaches are useful if we need a fully explicit or offline trusted-root artifact, but this failure is caused by Cosign using--new-bundle-formatbefore its normal trust-root cache has been initialized. Since each job installs and uses Cosign in the same runner environment, initializing Cosign after install lets Cosign populate its own TUF cache and keeps the fix local to these workflows.