Bonus anti-traffic analysis hack: new wrapped message is always sent
to: postmaster(_at_)recipient(_dot_)com with subject: encrypted message, real
recipient and subject recovered from Subject: and DKIM-Encrypted-To:
headers in the encapsulated message.
Use RFC 2442? Dan Newman had intended from the start that RFC 2442 could be
combined with "something else" to provide end-to-end encryption of the
envelope.
I suppose so, although it seems that just sticking Return-Path: and
Delivered-To: lines at the top of the message is all it needs to do before
encrypting.
With 2442, either it'd be doubly wrapped, an application/batch-SMTP inside
an application/dkim-encrypted. or it'd be a modified batch-SMTP, in which
case it's probably not worth the effort unless people want to be able to
send wrapped batches of messages.
Regards,
John Levine, johnl(_at_)taugh(_dot_)com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.
_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp