[Enigmail] Signature checks fails so often

[Noiano]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Patrick Brunschwig wrote:
> Cristian KLEIN wrote:
>> 2007/11/5, Noiano <noiano at x-privat.org>:
>> John W. Moore III wrote:
>>>>> Bob Henson wrote:
>>>>>> Noiano wrote:-
>>>>>>> Noiano wrote:
>>>>>>>> Hi everybody
>>>>>>>> I am using Enigmail 0.95.5 and very often the signature attached to
>>>>>>>> messages are not valid. This is quite a bit annoying because I have
>>>>>>>> to re send the message to the recipient.
>>>>>>>> How can I solve this?
>>>>> Another possibility is that You have require-cross-certification enabled
>>>>> and the Sigs that don't verify are ones where the Key Owner hasn't cross
>>>>> certified their sub-Keys. :-\
>>>>>
>> I don't even know what that is :-) so I think this is not the
>> problem. If it was all messages should have invalid signature
>> instead of "many". The latest message I sent with an invalid
>> signature can be found here:
>> http://www.sikurezza.org/ml/msg15881.html. I have tried to resend it
>> again and again but the signature is *always* invalid. What's wrong
>> with that message? It is pure plain text.
> 
>>> Hi,
>>> I know what your problem is. It came first into my mind when I saw
>>> that you used diacritics in your message. Suppose 
ex" is the message
>>> from the site UTF-8 encoded. Then
>>> cristi at hades:~$ export LANG=en_US.UTF-8
>>> cristi at hades:~$ cat ex | gpg --verify
>>> gpg: Signature made Sun 04 Nov 2007 12:09:09 AM EET using DSA key ID AB10E8D2
>>> gpg: BAD signature from "Noiano <noiano at lavabit.com>"
>>> However, if I convert this message to latin1:
>>> cristi at hades:~$ cat ex | iconv -t latin1 | gpg --verify
>>> gpg: Signature made Sun 04 Nov 2007 12:09:09 AM EET using DSA key ID AB10E8D2
>>> gpg: Good signature from "Noiano <noiano at lavabit.com>"
>>> gpg:                 aka "Noiano <noiano at x-privat.org>"
>>> gpg:                 aka "Marco Didonna <marco.didonna at autistici.org>"
>> So, the problem is encoding mismatch. Enigmail seems to sign the
>> message as if it was written in latin1, but someone (either the
>> receiver or the sender) convers this message to UTF-8.
> 
> Exactly, that's the issue. The problem is that Enigmail could handle
> this in the past (that is to say with v0.95.3 and earlier), but I
> introduced a regression bug here :-(
> 
> -Patrick
> 
That's why enigmail has *always* worked for me :-) . It is good to
have found this out.

Noiano
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iE8DBQFHL3Lt+JjGoasQ6NIRCLLbAN991hw2ffgz/tCxgvDpNxIOJRXt2hsfEVSE
2hyfAN44qQMRBIOxoNGba2Pibf1c/4k1708bL2Hg5yqj
=4FGt
-----END PGP SIGNATURE-----