Re: pgg doesn't seem to like me

[jam@jamux.com (John A. Martin)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>>>>> "Simon" == Simon Josefsson
>>>>> "Re: pgg doesn't seem to like me"
>>>>>  Thu, 10 Oct 2002 02:13:38 +0200

    Simon> Does this patch help?

    Simon> --- mml2015.el.~6.53.~ 2002-10-04 00:56:39.000000000 +0200
    Simon> +++ mml2015.el 2002-10-10 00:33:58.000000000 +0200
    Simon> @@ -662,6 +662,9 @@
    Simon>  	(if (condition-case err
    Simon>  		(prog1
    Simon>  		    (pgg-decrypt-region (point-min)
    Simon>  		    (point-max))
    Simon> + (goto-char (point-min))
    Simon> + (while (search-forward "\r\n" nil t)
    Simon> + (replace-match "\n" t t))
    Simon>  		  (setq decrypt-status
    Simon>  			(with-current-buffer
    Simon>  			mml2015-result-buffer
    Simon>  			  (buffer-string))))

With that patch in place my xemacs process disappeared while trying to
verify an armored PGP signed message that was also QP encoded.

,----[ On the command line: GnuPG-1.2.0 ]
| jam@athene:~/tmp$ cat ~/Mail/gnupg-users/9608|gpg --verify -vv
| gpg: armor: BEGIN PGP SIGNED MESSAGE
| gpg: armor header: Hash: RIPEMD160
| :packet 63: length 11 - gpg control packet
| gpg: armor: BEGIN PGP SIGNATURE
| gpg: armor header: Version: GnuPG v1.2.0 (GNU/Linux)
| gpg: armor header: Comment: Keys- http://www.geocities.com/burns98/rb_pub_keys.txt
| :literal data packet:
|         mode t, created 0, name="",
|         raw data: 0 bytes
| gpg: original file name=''
| gpg: CRC error; a4dfc8 - dc3a4d
| :signature packet: algo 17, keyid 84D2DA4D2CECAE1F
|         version 3, created 1034133720, md5len 5, sigclass 01
|         digest algo 3, begin of digest 5e 34
|         data: [159 bits]
|         data: [158 bits]
| gpg: quoted printable character in armor - probably a buggy MTA has been used
`----

Actually, I think the mail was from a buggy MUA.

,----
| User-Agent: KMail/1.4.1
| MIME-Version: 1.0
| Content-Transfer-Encoding: quoted-printable
`----

After reverting the patch a new XEmacs Gnus verified that mail and
another similar mail without incident.

>>>>> "jam" == John A Martin
>>>>> "Re: pgg doesn't seem to like me"
>>>>>  Thu, 10 Oct 2002 00:55:27 -0400

    jam> Since the encrypted messages look OK when decrypted on the
    jam> command line maybe something wrong is happening after gnus
    jam> decrypting?

Also, I see no extraneous ^M line ending characters when verifying
armored signed mail, KMail broken armored mail, or pgpmime signed mail
_from the wild_

I see no extraneous ^M in the product of Gnus decryption of armored
"PGP MESSAGES" (no mime) from the wild.  I don't see mail from the
wild pgpmime encrypted to me because, so far, I don't do MIME in
public.

Another point.  When my Gnus decrypts a my Gnus pgpmime signencrypt'ed
message that will show extraneous ^M characters, the minibuffer shows
something like

,----
| Unknowm encoding quoted printable ^M; defaulting to 8bit
`----

I do not see this when decrypting Gnus pgp(no-mime).

How can I get closer to this (these) problem(s)?

        jam

-----BEGIN PGP SIGNATURE-----

iEYEARECAAYFAj2llKoACgkQUEvv1b/iXy8p5gCePzjoQbnFOvLtB9tO9g5YBEp5
eRYAn1FnWROa7uckr9bSKx5qVSGlToP8
=55V6
-----END PGP SIGNATURE-----