v4.0.0 - Sign Images and SLSA-Provenance #98
JeroenKnoops
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Sign Images with Cosign
Now you can use Cosign to sign images.
Add
sign: true
to the arguments and provide the cosign environment variables and the image will be signed.You can generate a key-pair with cosign by doing the following thing:
Store the values as GitHub Secrets in
COSIGN_PRIVATE_KEY
,COSIGN_PASSWORD
andCOSIGN_PUBLIC_KEY
and you are ready to go.See: https://github.com/philips-software/docker-ci-scripts#signing-the-image
You can verify an image by doing the following thing:
Create SLSA-Provenance
You can create a SLSA-Provenance file. This feature is using https://github.com/philips-labs/slsa-provenance-action.
Add
slsa-provenance: true
to the arguments and aprovenance.json
file is created.The filename is exported as output in
slsa-provenance-file
.See: https://github.com/philips-software/docker-ci-scripts#with-slsa-provenance
Attach SLSA-Provenance to Image
When you are creating the SLSA-Provenance file and you provided the sign arguments and cosign environment variables, the SLSA-provenance file will be attached to the image.
You can verify the provenance by doing the following thing:
Push indicator output
When the image was pushed to a registry, this indicator
push-indicator
is set totrue
.Digest and tags outputs
container-digests
andcontainer-tags
are set when images are pushed.What's Changed
Dependency Updates
New Contributors
Full Changelog: v3.3.2...v4.0.0
This discussion was created from the release v4.0.0 - Sign Images and SLSA-Provenance.
Beta Was this translation helpful? Give feedback.
All reactions