[Enigmail] How are your signed content in ISO-8859-1 ???

[Maximilien Cuony [The_Glu]]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

> Interesting, your signature failed too ... :-( I don't think that I'
> m doing something special, I simply pass the message to GnuPG.

Yep, I didn't use the new FireGPG system so it's "normal"

Problem is not FireGPG signs to engimail, problem is sign sended by 
enigmail in iso-blalba, where he don't encode in base64 (but in 
8bits). When engimail make sign in base64 everything is ok ;)

Regards,
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: http://getfiregpg.org

iEYEARECAAYFAklqG2cACgkQjKKs5/FTCjWedwCdH2wTIyUqII+l8KhwquSWI1Kp
V9AAniBVyVTeuk1oGWuztUCmdV4PQ5WY
=Ne6q
-----END PGP SIGNATURE-----


On Sun, 11 Jan 2009 17:08:51 +0100, Patrick Brunschwig
<patrick at mozilla-enigmail.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Maximilien Cuony [The_Glu] wrote:
>> Hello,
>> 
>> I'm a FireGPG developer and as we slowly support openpgp/mime, I'm
trying
>> to make FireGPG compatible with Enigmail (when Enigmail send a mail to
>> FireGPG)
>> 
>> So in most of cases, it's work.
>> 
>> - When the mail is send in openpgp/mime, it's work. (Youpie °o°)
>> - When the mail is send with an inline sign, without special chars
>> (ééàà) it's works
>> - When the mail is send with an inline sign, with very-special chars
>> (Japanese, etc..) it's works (mail send in utf-8)
>> 
>> But. If I send a mail with special chars (French accents), with an
inline
>> sign, it's dosen't works.
>> 
>> It's doesn't work only with firegpg,  if I copy/paste the sign directly
>> to
>> gpg too. I tried everything, like --charset, copy message from original
>> source, etc...
>> 
>> Enigmail seem to be alone to successful verify the sign and I can't see
>> what Enigmail send to gnpg (except --charset UTF-8, strange...)
> 
> Hi, and nice to meet you :-)
> 
> the option --charset UTF-8 only defines that User ID's etc should be
> printed by GnuPG in UTF-8; the parameter has no influence on the
> processing of the mail content.
> 
>> So HOW do you verify this kind of signatures oO ?
> 
> Interesting, your signature failed too ... :-( I don't think that I'm
> doing something special, I simply pass the message to GnuPG.
> 
> But could it be that the problem is not related to éàè etc, but rather
> to the way the "-- " is passed to GnuPG? According to RFC 4880, spaces
> at the end of a line are forbidden and will cause the signature to fail
> verification. Therefore you should either sign the base64 message, or
> you have to use quoted-printable if you want to have spaces at the end
> of a line (and sign/verify the quoted-printable mail).
> 
> - -Patrick
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iQEVAwUBSWoZkXcOpHodsOiwAQITyQgAvYAlrW3RwaRUQ9qudynGyu9oqdQJoRki
> SXSHC/z5owVGtY15gVBaQMt8a+YH68AwQUII8AQnchkgRpQcNhFNGf3O4OuCFOTa
> 6J5EMLMyx64KF+MlRhoKWHyFV89uQz/XF3XhUl21KiLJasXIEtPILUyIXIb1QAKp
> 5lEGQtVoiEcTBEQSlfKOtS5G6kkT/8MnzKNDUaQ3m1dKFgI1J0gNt2ugLBOriV7s
> 6qGFCsUDHFmmPpSarplizElmNKjraK1+o/sHR8bDFFmRCUO2p7zGsDEH2139EsaJ
> 6vhr6Suc0LoaYyX3itOcNKCZz3Bo2AFZVQseUhtYUO+I3CHwQNxnEQ==
> =nn19
> -----END PGP SIGNATURE-----
> _______________________________________________
> Enigmail mailing list
> Enigmail at mozdev.org
> https://www.mozdev.org/mailman/listinfo/enigmail

-- 
Maximilien Cuony [The_Glu]
http://theglu.org