Re: check-traditional-pgp oddity
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dale Woolridge wrote:
> On 16-Sep-2003 13:14 Todd wrote:
> | I just noticed something strange with mutt 1.5.4's handling of an inline pgp
> | message. A message on the gnupg-users list began like this (indented so as
> | to hopefully not induce the same odd behavior I'm trying to explain):
>
> Have you tried piping the message to gpg w/o using mutt?
I hadn't done that, but in trying it just now, it behaves as expected, the
text is all there.
I had run mutt with -n -F /dev/null before which gave me an "Error: unable
to create PGP subprocess!" message before the normal "BEGIN PGP SIGNED
MESSAGE" output. So in that case, I knew that gpg hadn't touched the
message and yet the little korn script was missing. That convinced me that
somewhere along mutt's mutt_check_traditional_pgp code path was where the
text was getting stripped.
- --
Todd OpenPGP -> KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp
============================================================================
Conscience: the inner voice which warns us that someone may be looking.
-- H. L. Mencken
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl.
iD8DBQE/Z1Ysuv+09NZUB1oRAoFGAJ0TLFu3PuJA65C4YYw50gM4Td/AiwCfXpDK
Z5VmuODdsxhYMaFb9L370Ec=
=Y94T
-----END PGP SIGNATURE-----