-
Notifications
You must be signed in to change notification settings - Fork 60
Enable SIgned Releases #553
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
Comments
@liamfallon @johnbelamaric we can enable signed releases by following the steps mentioned over here |
Hey @VedRatan, it would be better to sign the container images using cosign so that we do not depend on Github specific signing/logs infrastructure. Cosign and corresponding transparency logs are maintained by Sigstore and this is backed by Open SSF. I would bring this up in the Rx Scope discussion meeting tomorrow. |
Hi! @nyrahul and @VedRatan we're signing released images since first release using cosign just not using ephemeral keys but a fixed key. Signature is uploaded as artifact to docker hub, for example: |
Hi @radoslawc I would like to work on this. |
Hey @radoslawc,
postsubmits:
nephio-project/free5gc:
- name: build-push-image-free5gc-operator-release-conf
...
...
containers:
...
- name: cosign
image: ttl.sh/cosign:24h
args:
- nephio/free5gc-operator:${PULL_BASE_REF}
env:
- name: COSIGN_PRIVATE_KEY
valueFrom:
secretKeyRef:
name: cosign-private-key
key: COSIGN_PRIVATE_KEY
- name: COSIGN_PASSWORD
valueFrom:
secretKeyRef:
name: cosign-private-key-passwd
key: COSIGN_PASSWORD
... Is my understanding correct? |
https://clomonitor.io/docs/topics/checks/#signed-releases-from-openssf-scorecard
See: #536
The text was updated successfully, but these errors were encountered: