Skip to content

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

Closed
gauteh opened this issue Feb 22, 2017 · 8 comments
Closed

Inline PGP / GPG #289

gauteh opened this issue Feb 22, 2017 · 8 comments
Labels

Comments

@gauteh
Copy link
Member

gauteh commented Feb 22, 2017

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:

@hugoroy
Copy link
Contributor

hugoroy commented Mar 1, 2017

I think that's the right approach! Accept (reasonably) everything and be strict in what you send ;-)

@gauteh
Copy link
Member Author

gauteh commented Mar 2, 2017 via email

@hugoroy
Copy link
Contributor

hugoroy commented Mar 2, 2017 via email

@gauteh
Copy link
Member Author

gauteh commented Mar 14, 2017

@gauteh
Copy link
Member Author

gauteh commented Sep 21, 2017

I'm going to close this. Too low priority.

@gauteh gauteh closed this as completed Sep 21, 2017
@mxmehl
Copy link
Contributor

mxmehl commented Sep 21, 2017

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.

@gauteh
Copy link
Member Author

gauteh commented Sep 21, 2017 via email

@gauteh
Copy link
Member Author

gauteh commented Jun 8, 2018

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.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants