-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, 12 Dec 2000, Werner Koch <wk(_at_)gnupg(_dot_)org> wrote:
On Tue, 12 Dec 2000, Ian Bell wrote:
newsgroups/mailing lists - the problem being that the "-- " gets stuffed
to "- -- " with the result that recipients' clients will no longer
The preferred way to encapsulate OpenPGP messages in mail is by using
MIME as defined in RFC2015.
In an ideal world, PGP/MIME would be the only way anyone would send PGP
in email...
No need for the old fashioned cleartext
signing.
...however, the reality is that most clients (in terms of numbers
deployed) seem not to be able to cope.
We have been asked to munge the dash-stuffed clear text as in practice
the use of PGP/MIME signed messages causes more complaints than clear-
signed messages, but clear-signing messages causes complaints about
broken sig-seps :-(
The question is, how do openPGP clients cope with such messages and what
It is a matter of the MUA to handle this right. Mutt for example
does remove the dash escaping even when it does not verify the
signature.
As does Turnpike. However, it will be the openPGP client that has to
deal with the clear-text message with dash-stuffing that breaks RFC-
2440. As an example I have signed this message and broken the dash-
stuffing (behind Turnpike's back, I might add!). I'd be interested if it
causes any problems.
--
Ian Bell T U R N P I K E
-----BEGIN PGP SIGNATURE-----
Version: PGPsdk version 1.7.1
iQA/AwUBOjZUxb3aNYn/fmK7EQLGcACdH2kUCbQH06wWa/9Ap/6XaaWpdBMAnj1G
IoOPuvpMBehwVZFZ52sEW63d
=yQWW
-----END PGP SIGNATURE-----