-
Notifications
You must be signed in to change notification settings - Fork 46
docs: Clarify that container signatures expect a single signature packet #426
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.
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
Conversation
2f7e230 to
c5c2dfa
Compare
TomSweeneyRedHat
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@mtrmac PTAL
mtrmac
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, makes sense to clarify this.
image/docs/containers-signature.5.md
Outdated
| (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). | ||
| - The blob MUST contain one single "Signature Packet" as defined in RFC 4880 section 5.2. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
‘must not contain multiple ”Signature Packet”s’, to be unambiguous?
As a non-native speaker, I don’t read “must contain one” to prohibit “must not contain two”; the “single” sort of does imply uniqueness, but that kind of grammar is not taught in introductory English courses.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mtrmac I just reworded it
Clarify that OpenPGP container signatures are expected to contain exactly one signature packet. This clarification is necessary because, according to RFC 4880, a "Signed Message" may contain a sequence of signature packets. This case might not be correctly handled by the existing verification software. Signed-off-by: Roberto Hueso Gomez <roberto@robertohueso.org>
c5c2dfa to
6a39ff0
Compare
mtrmac
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Clarify that OpenPGP container signatures are expected to contain a single signature packet.
This clarification is necessary because, according to RFC 4880, a "Signed Message" may contain a sequence of signature packets. This case might not be correctly handled by the existing verification software.
More info on this on this PR in #423