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> jam@jamux.com (John A. Martin) writes:
    >> Using (mml-signencrypt-style "pgpmime" 'combined) and
    >> (mml-signencrypt-style "pgp" 'combined) with a cvs gotten about
    >> 14:00 GMT Oct 5:

    Simon> Shouldn't those things be customized instead of calling
    Simon> functions, btw?  I made the `mml-signencrypt-style-alist'
    Simon> variable customizable.  Calling the functions should still
    Simon> work though.

Somewhere it was stated to use the `mml-signencrypt-style' function.
I'm no great fan of custom and neither it seems is the author of the
the XEmacs-21.4.8 sample.init.el. :)

    >> Signed only pgpmime messages look ok when mailed to myself and
    >> verified by gnus.

Still OK using XEmacs-21.4.8 (xemacs21-nomule_21.4.8-2_i386.deb) and
the cvs with lisp/ChangeLog/6.1598/Thu Oct 10 01:40:39 2002// with gpg
as follows.

,----[ GnuPG-1.2.0 gpg.conf ]
| no-greeting
| lock-once
| no-version
| openpgp
| default-key 0xbfe25f2f
| #no-default-keyring
| 
| keyserver x-hkp://wwwkeys.us.pgp.net
| keyserver-options auto-key-retrieve include-disabled include-revoked
| 
| #show-photos
| 
| # "Encrypt to self"
| encrypt-to 0xbfe25f2f
| 
| # Non-compliant to OpenPGP rfc2440
| escape-from-lines
| 
| # Read only keyrings
| keyring /usr/share/keyrings/debian-keyring.gpg
| keyring /usr/share/keyrings/debian-keyring.pgp
| 
| group peon@jamux.com=0xb870dab6 0xd5c296f2 0x7df7d271
`----

    >> Encrypted pgpmime (combined) messages mailed to myself show
    >> extraneous Ctrl-M characters at the end of all body lines.

    Simon> I can't reproduce this with PGG and GnuPG CVS.  Do you use
    Simon> PGG?  Which OpenPGP implementation?  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))))

pgg gives no change from before with the setup above with or without
the patch.  As before, the same messages decrypted by gpg on the
command line or by mhe/mailcrypt are OK.

    >> Signed only pgp messages mailed to myself are QP encoded and
    >> show extraneous Ctrl-M characters at the end of all body lines
    >> when verified and displayed by gnus.

    Simon> I think I fixed the QP, but I don't see the ^M.

Still same as before with or without the patch above.

    >> Encrypted pgp (combined) messages are not encoded, signed, nor
    >> encrypted.

    Simon> Or sent, as it generated a elisp error, I presume.  I think
    Simon> I fixed this.

Before, no elisp error and the messages were sent plaintext!

Now encrypted pgp (combined) messages are signed and encrypted but
when decrypted in gnus show extraneous Ctrl-M characters at the end of
all body lines.  The same messages decrypted by gpg on the command
line or by mhe/mailcrypt are OK.

    >> cat textfile|gpg -sat|/usr/sbin/sendmail myself; cat inbox/1
    >>
    >> cat textfile|gpg -seatr myself|/usr/sbin/sendmail myself
    >> cat inbox/1|gpg
    >>
    >> In other words, why should gnus pgp muck with pgp not mime?
    >> Mhe/mailcrypt does not.  Gnus/mailcrypt does not[1].

    Simon> Do you still see any differences?

No change from before except that the pgp(no-mime) encrypted messages
are signed and encrypted but gnus shows the ^M.  The pgp(no-mime)
signed messages are QP and so not verified by gpg on the command line.

Is there an easy way to tell for sure that the messages are being
processed by pgg and not by anyone else that should not be involved.

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

        jam

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

iEYEARECAAYFAj2lCDQACgkQUEvv1b/iXy90AwCfef1m3bl+mmLOUI2yjw8nIk+P
K1EAnArCaVEppnyxRUvZ5GSkG3+O1bPC
=+9LI
-----END PGP SIGNATURE-----