podman image verify vs. external Cosign for multi-signature images

Question

Goal
A container workflow using Podman 4.0+ requires validation of OCI image signatures. The images in this environment are signed by multiple entities, such as a build pipeline and a security auditor, resulting in multiple signatures per image.

Constraints
The built-in podman image verify command leverages the Cosign library but is documented to process only the first signature in the signature list. In contrast, the standalone Cosign CLI supports full verification of all signatures, keyless verification, and attestations, but introduces an external binary dependency and separate key management.

Does podman image verify silently ignore subsequent signatures, or does it return a specific warning when multiple signatures are present?
Is there a configuration within Podman 4.x to enable the evaluation of all signatures, or is the external Cosign CLI the only documented method for multi-signature validation?

Tasadduq Burney · Answer

Direct answers Question 1: podman image verify does not silently ignore subsequent signatures. It emits a warning — multiple signatures found, only the first will be verified — then proceeds to validate only the first signature. If that first signature is valid, the command exits with code 0. Question 2: No configuration flag or option in Podman 4.x enables full multi-signature evaluation. The documented and supported path for verifying all signatures, keyless flows, and attestations is the standalone Cosign CLI. Why this matters In a multi-signer workflow (e.g., build pipeline + security auditor), relying solely on podman image verify creates a false sense of security: the auditor's signature is never checked. Worse, if the first signature is invalid but a later one is valid, Podman fails even though a valid signature exists. Verified behavior (Podman 4.x) Internally uses the Cosign library but iterates only over the first signature in the list. Warning is printed to stderr; exit code reflects only the first signature's validity. No --all-signatures, --policy, or similar flag exists in 4.x releases. When to use external Cosign Use the Cosign CLI when you need: Verification of every signature on an image (cosign verify --key && cosign verify --key ) Keyless verification via OIDC identity tokens Attestation verification (cosign verify-attestation) Threshold or quorum policies (combine with Rekor, Connaisseur, or custom policy engines) Quick verification you can run today # 1. Confirm no multi-signature flag exists podman image verify --help # 2. Create a test image signed twice with different keys cosign generate-key-pair # repeat for key2 cosign sign --key cosign.key $IMAGE cosign sign --key cosign2.key $IMAGE # 3. Observe Podman's warning and exit code podman image verify $IMAGE # Expected: warning printed, exit 0 if first sig valid # 4. Verify both signatures independently with Cosign cosign verify --key cosign.pub $IMAGE cosign verify --key cosign2.pub $IMAGE One diagnostic detail that changes the recommendation What Podman version are you running? The single-signature limitation is explicitly documented for the 4.x series; Podman 5.x may introduce changes. Run podman --version to confirm before committing to a workflow.

podman image verify vs. external Cosign for multi-signature images

Goal

Constraints

1 answer

Direct answers

Why this matters

Verified behavior (Podman 4.x)

When to use external Cosign

Quick verification you can run today

One diagnostic detail that changes the recommendation

Your perspective belongs here.

0 question comments