Skip to content
This repository was archived by the owner on Sep 26, 2026. It is now read-only.

docs(security): document the cosign signature-format requirement - #1071

Merged
castrojo merged 1 commit into
projectbluefin:testingfrom
hanthor:docs/signing-cosign-bundle-format
Aug 9, 2026
Merged

castrojo merged 1 commit into
projectbluefin:testingfrom
hanthor:docs/signing-cosign-bundle-format

Conversation

@hanthor

@hanthor hanthor commented Aug 9, 2026

Copy link
Copy Markdown
Member

Documents the signature-format requirement that containers/image imposes on us, and why a green cosign verify is not evidence an image is verifiable by podman or bootc switch.

Context: every projectbluefin image built since ~2026-06-08 is signed in a format podman cannot see, because cosign 3.x flipped --new-bundle-format to default true and writes signatures as OCI 1.1 referrers instead of the legacy sha256-<digest>.sig tag. CI reported signing as successful throughout, because cosign verify accepts both formats.

This PR is docs-only — no workflow or build change. It also serves as the consumer-validation PR for projectbluefin/actions#420 per that repo's docs/skills/consumer-validation.md.

containers/image (podman, skopeo, bootc switch) discovers signatures only via
the legacy sha256-<digest>.sig tag, never the OCI 1.1 referrers API — which
GHCR does not implement in any case.

cosign 3.x defaults --new-bundle-format=true, which writes signatures as OCI
referrers instead, producing images that cosign verify accepts and podman
rejects. Record why a green cosign verify is not sufficient evidence, and how
to check the tag that actually matters.

Refs projectbluefin/common#977, projectbluefin/actions#420
@hanthor
hanthor requested a review from a team as a code owner August 9, 2026 03:42
@castrojo
castrojo merged commit 550678a into projectbluefin:testing Aug 9, 2026
4 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants