-
-
Notifications
You must be signed in to change notification settings - Fork 66
Inline PGP / GPG #289
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
I think that's the right approach! Accept (reasonably) everything and be strict in what you send ;-) |
Hugo Roy writes on mars 2, 2017 0:13:
I think that's the right approach! Accept everything and be strict in what you send ;-)
Yes, the problem is that parsing all the different formats of inline pgp
is royal pain in the neck. It will require a lot of effort to get it
right unfortunately.
|
↪ Gaute Hope / mars 2, 2017 8:56:
Hugo Roy writes on mars 2, 2017 0:13:
> I think that's the right approach! Accept everything and be strict in what you send ;-)
Yes, the problem is that parsing all the different formats of inline pgp
is royal pain in the neck. It will require a lot of effort to get it
right unfortunately.
It could be interesting to see how Mailpile does it. They probably have
run into many GPG issues recently.
|
Good news! GMime gets inline PGP in version 3.0: |
I'm going to close this. Too low priority. |
Hm, that's sad. I still get many inline-gpg signed messages and they are a real PITA to read. Encrypted messages are rarer fortunately. |
Max writes on september 21, 2017 15:18:
Hm, that's sad. I still get many inline-gpg signed messages and they are a real PITA to read. Encrypted messages are rarer fortunately.
Maybe the new decrypt_message code can handle it more easily. Shouldn't
be too hard to write a small test case to see.
|
Note to self: If we support this, makes sure to handle inlined PGP (separate iframe?) as safely as regular PGP/MIME w.r.t. #499. |
This is a bad idea, but there is still a lot of clients sending this around. We will never support sending inline PGP, but might support parsing in some cases.
Resources:
The text was updated successfully, but these errors were encountered: