On 01/16/2009 04:43 PM, Brad Knowles wrote:
I don't think it broke the signature, I think what happened is that it
hasn't been encapsulated in the correct manner.
*nod*
At the very least, you can do a message/rfc822 bodypart, and that should
guarantee that the signature is not broken, assuming that there's no
changes in whitespace encoding, etc....
However, I don't know how most MUAs would handle that in a signed
message. A more intelligent encapsulation format should hopefully
address that issue.
Agreed. I'm not sure how receiving MUAs would handle this. I know that
a message/rfc822 MIME body part is how messages are forwarded (as
attachments) so they should be ok. At least I can forward a message as
a message/rfc822 MIME body part and then later strip away everything but
the contents of the message/rfc822 MIME body part and the message will
then be able to be validated again. I will play with forwarding an
S/MIME signed / encrypted message and let you know what my MUAs (of
choice) do with the message/rfc822 MIME body part.
Grant. . . .
------------------------------------------------------
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
