From 847d5c57ab7887a6940467338d0cc421f73edee7 Mon Sep 17 00:00:00 2001 From: Marek Simek Date: Thu, 7 May 2026 11:40:52 +0200 Subject: [PATCH] docs: image/signature: Document ASCII Armor Message not supported Fixes: #637 Signed-off-by: Marek Simek --- image/docs/containers-signature.5.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/image/docs/containers-signature.5.md b/image/docs/containers-signature.5.md index b43c1ec9ce..3e7298dc6b 100644 --- a/image/docs/containers-signature.5.md +++ b/image/docs/containers-signature.5.md @@ -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.