On 2001-03-05 09:28:14 -0800, John W Noerenberg II wrote:
Have you considered the implications of format=flowed (rfc2646)?
Specifically:
4.6. Digital Signatures and Encryption
If a message is digitally signed or encrypted it is important that
cryptographic processing use the on-the-wire Format=Flowed format.
That is, during generation the message SHOULD be prepared for
transmission, including addition of soft line breaks, space-stuffing,
and [Quoted-Printable] encoding (to protect soft line breaks) before
being digitally signed or encrypted; similarly, on receipt the
message SHOULD have the signature verified or be decrypted before
[Quoted-Printable] decoding and removal of stuffed spaces, soft line
breaks and quote marks, and reflowing.
That's perfectly compatible with draft-05: Trailing white space will
be protected by the quoted-printable encoding of the flowed text, so
there is _no_ trailing whitespace in the signed material as the hash
algorithm sees it.
--
Thomas Roessler <roessler(_at_)does-not-exist(_dot_)org>
This message may have been certified to be possibly virus-free.