-
Notifications
You must be signed in to change notification settings - Fork 84
feat: cleartext framework support #328
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
Signature(StandaloneSignature), | ||
} | ||
|
||
impl Any { |
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.
This name clashes with std::any::Any
. I wonder if the name is worth changing.
I fear the RFC doesn't offer terminology for "any kind of PGP thing". The most generic objects it names are "Messages" and "Keys" (neither of which includes cleartext messages).
Attempting to brainstorm alternative names: (Open)PgpData
, (Open)PgpContent
.
I currently have no idea that I'm excited about.
(I don't think this kind of generic reader needs to be limited to armored data, so I would tend to not use "armor" in the naming)
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.
I think I am going to stick with Any
for now, and wait for better suggestions :)
828da68
to
fb5a09c
Compare
* csf: add test * csf O_o * xx: this should not not fail * anything but whitespace is not ok after the armor footer * use expect in signed_text
fb5a09c
to
11ff3c1
Compare
thanks to @hko-s for tips and existing work.
composed::CleartextSignedMessage
composed::Any
for dealing with arbitrary armor based contentCloses #122