I thought I would write a filter for Pine users to be able to deal
with PGP-MIME signed messages.  It struck me that the concept should
be fairly simple.  I hacked together a quick shell script that does
the following:

 - separate the text of the message
 - separate the PGP signature of the message
 - gpg --verify them

Only when I run the gpg --verify, it fails.  I'm not sure why.  I'm
including in the message everything between (but not including) the
LAST Content-Blah: header and the mime boundary.  I also tried
removing the trailing and leading blank lines.  No comination of that
helped.

Is there some magic trick?  Does mutt sign some other portion of the
text message, or include mime headers?  This would make no sense to
me, but I suppose it's possible.

What am I missing?

Note that the message I'm testing on is a plain text message, not
quoted printable, so the conversion shouldn't be an issue, if it ever
is...

-- 
Derek Martin               [EMAIL PROTECTED]    
---------------------------------------------
I prefer mail encrypted with PGP/GPG!
GnuPG Key ID: 0x81CFE75D
Retrieve my public key at http://pgp.mit.edu
Learn more about it at http://www.gnupg.org

Attachment: msg23047/pgp00000.pgp
Description: PGP signature

Reply via email to