docs: image/signature: Document ASCII Armor Message not supported#839
Merged
Merged
Conversation
mtrmac
reviewed
May 11, 2026
Fixes: containers#637 Signed-off-by: Marek Simek <msimek@redhat.com>
simek-m
force-pushed
the
637-doc-no-ascii-armor-signature
branch
from
ee7e824 to
847d5c5
Compare
|
A quick clarification: if ASCII Armor is not to be used, how is the signature encoded? As-is, it's binary packet data, and unsuitable for JSON, is it not? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR updates the
containers-signature(5)man page with the clarification that the ASCII-armored container OpenPGP signatures are not supported.Fixes: #637