From: openpgp [mailto:openpgp-bounces(_at_)ietf(_dot_)org] On Behalf Of
Phillip
Hallam-Baker
If we are doing an overhaul of PGP, one of the things that needs
fixing is a way to send signed messages that does not get in the way.
http://www.explainxkcd.com/wiki/index.php/1181:_PGP
'If this is there, its probably fine'.
Problem with the ASCII approach is that most of the important stuff in
mail is in the attachments.
One solution is PGP Partitioned format, which supports in-line signatures for
ASCII bodies and detached signatures for other email content:
http://www.ietf.org/mail-archive/web/openpgp/current/msg01811.html
When PGP was invented, mail had huge amounts of lossage that would
break things for no reason. That is no longer the case. Most mail
transport is 8-bit clean.
A way to use a PGP key for DKIM would be nice. And PGP should make use
of the same code paths in MIME that mean that S/MIME headers don't get
in the way.
There is a standard for PGP/MIME clear-signing content and the result looks a
lot like S/MIME. Major S/MIME enabled mail clients (e.g. Microsoft Outlook and
Mozilla Thunderbird) render it nicely when PGP/MIME-aware software is absent so
I would consider that staying out of the way. See:
https://tools.ietf.org/rfc/rfc3156.txt
Using the above as a starting point, what aspect of a MIME signature's impact
is left to solve?
Cheers,
-Neil
_______________________________________________
openpgp mailing list
openpgp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/openpgp