On Mon, Mar 16, 2015 at 7:28 PM, Daniel Kahn Gillmor
<dkg(_at_)fifthhorseman(_dot_)net>
wrote:
Hi Albrecht--
Sorry for the late followup -- this has now been raised on
openpgp(_at_)ietf(_dot_)org, so i'm moving the follow up there.
On Sun 2015-02-22 13:14:36 -0500, Albrecht Dreß wrote:
I am currently working on the implementation of your proposal for Balsa
[1], and would like to add a few comments.
I'm glad to hear this!
Am 16.01.15 21:29 schrieb(en) Daniel Kahn Gillmor:
PGP/MIME messages are the only reliably structured mail OpenPGP e-mail
messages anyway [0].
As your proposal is fully transparent, I think it could also be used
for RFC 2633 S/MIME (i.e. multipart/signed;
application/pkcs7-signature as well as for application/pkcs7-mime).
yep, this seems correct to me, but i don't know enough about the S/MIME
world to take the proposal there. Maybe we should find some S/MIME
folks to chime in on this.
I am not sure I am an S/MIME person. But I would like to see this sort of
problem fixed in decently layered fashion that allows the same approach to
be used in either.
SMTP and HTTP share a problem of mixing up routing information (From, To,
Path) and Content meta data. If we could untangle the two in a repeatable
fashion, we can use the same approach to encrypt stored data blobs.
So one approach would be to take the content-metadata headers out of the
STMP section of the message and push them into the body of the message.
That would then make possible approaches where the subject line is
encrypted under one key and the content payload is encrypted under another.
_______________________________________________
openpgp mailing list
openpgp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/openpgp