-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 13 Jan 2002, Derek D. Martin wrote: > 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.
Read RFC 2015. :) > 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. The mime headers are defined to be included in the signature by RFC 2015. It's *also* require that the body still be in QP encoded form as well as that lines are terminated by \r\n instead of the unix standard of \n. All of this is explained in the RFC pointed to above. > 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... Check the line terminator as well as making sure you're including the mime headers. By following RFC 2015 by hand, I can verify a PGP/MIME encoded message. - --JT - -- [-------------------------------------------------------------------------] [ Practice random kindness and senseless acts of beauty. ] [ It's hard to seize the day when you must first grapple with the morning ] [-------------------------------------------------------------------------] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8QUBOlZQYYI16LJQRAkZ5AJwMqHp7QEpZD9UdbXdNYFEKVYOtqgCfZbH9 LsA58aZD/pJCSebP82bOJHw= =Pwc6 -----END PGP SIGNATURE-----
