Re: pgg doesn't seem to like me

[Simon Josefsson <jas@extundo.com>]

jam@jamux.com (John A. Martin) writes:

>     >> 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.

Hm. Can you make a proper bug report (M-x gnus-bug) so I can see which
emacs, operating system, etc you use, and other settings?  Or send me
an encrypted mail, then I can see if it is encrypting or decrypting
that is buggy.

>     >> 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.

Probably same bug.  Is the message properly verified otherwise?

>     >> 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.

That's probably good then, only the ^M bug left.

>     >> 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.  

Ok, maybe this is due to some combination of OS and emacs version that
I don't use.

> The pgp(no-mime) signed messages are QP and so not verified by gpg
> on the command line.

I recall some discussion about whether cleartext armored OpenPGP
messages should be QP'd or not when mml1991.el was added, and that the
outcome was that they should.  It seems ugly to me, and I don't see
why it would be necessary, but maybe I forgot.

> 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.

Other than checking the configuration or edebugging everything, I
don't know.

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

Yup.  Or your terminal is simply hiding the ^M's...