* Peter M?ller Neergaard <peter@xxxxxxxxxxxxxxxxxxx> [2004-01-29 15:47:00 -0500]: > When verifying a well-signed message, mutt will present the successful > gpg output, e.g., > > [-- Attachment #1 --] > [-- Type: multipart/signed, Encoding: 7bit, Size: 1.1K --] > > [-- PGP output follows (current time: Thu 29 Jan 2004 03:36:43 PM EST) --] > gpg: Signature made Thu 29 Jan 2004 02:28:29 PM EST using DSA key ID 6490CC10 > gpg: Good signature from "Peter M?ller Neergaard <peter@xxxxxxxxxxxxxxxxxxx>" > gpg: aka "Peter M?ller Neergaard <turtle@xxxxxxxxx>" > gpg: aka "Peter M?ller Neergaard <turtle@xxxxxx>" > gpg: aka "Peter M?ller Neergaard <turtle@xxxxxxxxxxxxxxx>" > gpg: aka "Peter M\xf8\x6cler Neergaard <turtle@xxxxxxxxx>" > gpg: aka "Peter M\xf8\x6cler Neergaard <turtle@xxxxxx>" > gpg: aka "[jpeg image of size 5212]" > [-- End of PGP output --] > > [-- The following data is signed --] > > ... > > [-- End of signed data --] > > but in the message area at the bottom it will report: > > PGP signature could NOT be verified. Maybe you need to change the value of $pgp_good_sign? -- John ! Why, then, should we grant government the Orwellian Buttery! capability to listen at will and in real time to our www.io.c! communications across the Web? om/~john! -- John Ashcroft, October 1997
Attachment:
signature.asc
Description: Digital signature