On 2000-05-11 09:44:28 +0100, Ian Bell wrote:
1) Simply state the problem, and indicate that for
one-pass processing, two hashes will have to be
prepared - one for binary-mode signatures and one
for text-mode signatures.
2) Mandate which form of signature must be used.
Trailing spaces are often significant in email/news
(sig-seps, RFC2646), so a binary-mode signature
might seem preferable. However, existing PGP/MIME
clients may be using either.
3) Define a "pgp-mode" parameter, pgp-mode=binary or
pgp-mode=text and ensure that new clients add the
parameter to the multipart/signed header. If the
parameter is missing (RFC2015 messages), then
one-pass clients will have to prepare two hashes.
Well... As a fourth possibility, we could mandate that
any trailing whitespace within body parts should lead to
the use of quoted-printable or base64, thus effectively
working around the problem. However, this is _not_
currently mandated by RFC 1847.
Actually, doing this is suggested in one of the example
messages, but for different reasons.
--
http://www.guug.de/~roessler/