Re: A permission to re-sign header
"John R Levine" <[email protected]> 18 Apr 2014 16:18:11 -0400
| Newsgroups | gmane.ietf.rfc822 |
|---|---|
| Message-ID | <[email protected]> |
>> It has to be more than that, it has to say that it's OK for >> foo.example.net to pass it along in modified form. > > Why? Why isn't the fact that I sent the mail directly to this thing enough > implicit permission for it to pass my message along in modified form? Is the > threat model here supposed to include preventing the workings of evil > mailing lists that I intentionally send mail to? Perhaps we're using different words to say more or less the same thing. There seems little point to adding the token if you don't expect the recipient to republish it. But I was wondering if there are things that are not mailing lists to which one sends mail and would be unhappy if they republished it in a way that shows your approval to do so. Maybe not. It certainly will be amusing if people send mail with the M-R header at the top and the confidential boilerplate nonsense at the bottom. Regards, John Levine, [email protected], Taughannock Networks, Trumansburg NY Please consider the environment before reading this e-mail. _______________________________________________ ietf-822 mailing list [email protected] https://www.ietf.org/mailman/listinfo/ietf-822
smime.p7s
(application/pkcs7-signature, 2.2 KB) - not displayed