-
Notifications
You must be signed in to change notification settings - Fork 112
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
Update cosign #1201
Update cosign #1201
Conversation
Signed-off-by: Natalie Arellano <[email protected]>
permissions: | ||
id-token: write |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
permissions: | ||
contents: write |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I updated the repo "Actions permissions" settings to use the more restrictive "Read repository contents and package permissions" instead of the more permissive "Read and write permissions", thus this is now required.
Signed-off-by: Natalie Arellano <[email protected]>
d606d00
to
cd39528
Compare
Signed-off-by: Natalie Arellano <[email protected]>
In #1201 we explicitly granted the needed permissions to the token, and we updated the repo settings to be the most restrictive. Now that the repo has been updated, the draft-release workflow is broken for minor versions less than 0.18.x. This change will allow us to continue to patch 0.17.x. Signed-off-by: Natalie Arellano <[email protected]>
…ons (#1256) In #1201 we explicitly granted the needed permissions to the token, and we updated the repo settings to be the most restrictive. Now that the repo has been updated, the draft-release workflow is broken for minor versions less than 0.18.x. This change will allow us to continue to patch 0.17.x. Signed-off-by: Natalie Arellano <[email protected]>
Summary
Updates GitHub actions workflows that use
cosign
to sign and verify lifecycle images to use keyless signing. This is the default as ofcosign
2.x.x and is considered more secure than signing with a long-lived private key. Note that thecosign verify
command for verifying signatures is also updated.When this is merged, we can remove
COSIGN_PASSWORD
andCOSIGN_PRIVATE_KEY
from repo secrets. We'll also need to update our Docker Hub page help text with the new information.Release notes
cosign
, use keyless signingRelated
Resolves #___
Context
Tested (with some effort) on fork: https://github.com/natalieparellano/lifecycle/actions