Re: check-traditional-pgp oddity
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
To follow up on my own post and offer a clue from my own testing...
I tried to recreate this locally by creating a message beginning with a
little for loop but I could not get the same behavior. I then diffed the
offending message and the one I created. I found was that the bad message
had a line containing a single space just after the PGP Hash: header line
instead of a blank line. Adding this space into my message produced the
same results (disappearing text). Seems strange that mutt would strip this
text, but perhaps it thinks that these lines are part of the OpenPGP header.
I think that this space after the Hash line may violate the OpenPGP spec,
but I'd have to look that up or ask on the gnupg-user list to be sure. I do
know that piping the message to gpg leaves the text intact, so mutt is being
more particular about the spec than gpg itself, if it's treating them as
OpenPGP headers. :-)
BTW, I had to manually edit the message to add the space after the hash line
since gpg wouldn't produce such a message. It always added a blank line
following the hash line.
- --
Todd OpenPGP -> KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp
============================================================================
The policy of the American government is to leave its citizens free, neither
restraining nor aiding them in their pursuits.
-- Thomas Jefferson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl.
iD8DBQE/Z16ouv+09NZUB1oRAuMiAKCNM1+QW9YPmEJ9HpIB5flFvYgYFgCguZbd
bi0Xlu67lppoSKwvTtgx8JA=
=iBwl
-----END PGP SIGNATURE-----