Skip to content

docs: image/signature: Document ASCII Armor Message not supported #839

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.

Sign up for GitHub

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

Merged
mtrmac merged 1 commit into from
May 12, 2026
+1 −1
Merged

docs: image/signature: Document ASCII Armor Message not supported #839

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion image/docs/containers-signature.5.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,7 @@ the consumer MUST verify at least the following aspects of the signature
- The blob MUST be a “Signed Message” as defined in RFC 4880 section 11.3.
(e.g. it MUST NOT be an unsigned “Literal Message”,
a “Cleartext Signature” as defined in RFC 4880 section 7,
or any other non-signature format).
any other non-signature format, and MUST NOT use ASCII Armor as defined in RFC 4880 section 6).
- The blob MUST NOT contain more than one "Signature Packet" as defined in RFC 4880 section 5.2.
- The signature MUST have been made by an expected key trusted for the purpose (and the specific container image).
- The signature MUST be correctly formed and pass the cryptographic validation.
Expand Down
Loading