Skip to content
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

Sign OCI-SIF (cosign/sigstore) #3492

Closed
dtrudg opened this issue Jan 21, 2025 · 0 comments · Fixed by #3510
Closed

Sign OCI-SIF (cosign/sigstore) #3492

dtrudg opened this issue Jan 21, 2025 · 0 comments · Fixed by #3510
Assignees

Comments

@dtrudg
Copy link
Member

dtrudg commented Jan 21, 2025

An OCI-SIF, containing an OCI container image, should be able to be signed using singularity sign.

The signature applied should be a standard cosign/sigstore signature.

@dtrudg dtrudg self-assigned this Jan 21, 2025
dtrudg added a commit to dtrudg/singularity that referenced this issue Feb 4, 2025
Add a new `--cosign` mode to `singularity sign`, which will apply a
cosign-compatible signature to a container image in an OCI-SIF, and
store the signature image in the OCI-SIF, using the name.ref
association defined by sylabs/oci-tools.

Unlike the upstream sylabs/oci-tools code, Singularity currently only
creates / considers OCI-SIF images that contain a single OCI image.
Consequently there is no signature handling for image indices in
Singularity at this point.

From this commit onwards, Singularity ignores cosign images in the
OCI-SIF when looking for an OCI image to execute, push etc. Older
versions of Singularity will error when attempting to execute a signed
image, as they expect only one image in an OCI-SIF, with no filtering
of non-executable cosign related images.

Fixes sylabs#3492
@dtrudg dtrudg closed this as completed in 8b2e5b9 Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant