General Error while checking message signature (Maybe I should has at Enigmail list)

John Clizbe John at
Thu Feb 12 17:23:19 CET 2009

Faramir wrote:
>   All the messages that caused this error had attached a signature.asc file.

That's a sign of a PGP/MIME message. The signature is put into another chunk of the
email than the message.

>   While I have modified my gpg default preferences, I did that some
> months ago, so I think this is not related to recent changes (I have not
> done any changes recently).
>   Any idea about what could be causing this error?

Misconfiguration on his end. PGP/MIME requires that the hash
algorithm be included in the MIME header. His message header specifies:

Content-Type: multipart/signed;
	protocol="application/pgp-signature"; micalg=pgp-sha1


Looking at the signature:

$ gpg --list-packets < malte-sig
:signature packet: algo 1, keyid CA3CCC060F278D6D
        version 4, created 1234428383, md5len 0, sigclass 0x00
        digest algo 3, begin of digest 7d 03
        hashed subpkt 2 len 4 (sig created 2009-02-12)
        subpkt 16 len 8 (issuer key ID CA3CCC060F278D6D)
        data: [1024 bits]

Digest algo 3 ==> RIPEMD160

His client says, "I'm signing with SHA-1," but then appends a RIPEMD160 signature.

That's what's causing this error.


John P. Clizbe                      Inet:John (a)
You can't spell fiasco without SCO. hkp://  or
     mailto:pgp-public-keys at

Q:"Just how do the residents of Haiku, Hawai'i hold conversations?"
A:"An odd melody / island voices on the winds / surplus of vowels"

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 677 bytes
Desc: OpenPGP digital signature
URL: </pipermail/attachments/20090212/d61069fe/attachment.pgp>

More information about the Gnupg-users mailing list