-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Carlos E. R. wrote:
The Friday 2007-12-28 at 11:21 -0000, G T Smith wrote:
<snip>
If I verify the signature the
Content-Type: text/plain; charset=ISO-8859-1
Ah.
Yes, I have noticed (rather I was told of this) that if my emails go out in English the signature verifies well in Thunderbird, but if they go in Spanish it doesn't verify. The difference is that in the second case the email uses utf-8.
A good email goes like this:
... User-Agent: Alpine 0.999999 (LSU 847 2007-12-06) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Status: RO X-Status: X-Keywords: X-UID: 2
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ...
A bad one goes like this:
... User-Agent: Alpine 0.999999 (LSU 847 2007-12-06) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-1463809023-467100771-1198265468=:24727" Status: RO X-Status: X-Keywords: X-UID: 3
---1463809023-467100771-1198265468=:24727 Content-Type: TEXT/PLAIN; format=flowed; charset=UTF-8 Content-Transfer-Encoding: 8BIT
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ...
But I haven't studied the thunderbird part of the problem. I know both kind of signatures verify well using kmail, for instance, so it is not my "fault".
The language/char set thing seems to be a known enigmail extension problem... (noticed references to it in passing while checking to see there were any references to this header problem on the enigmail site). I get the impression there is a work around... As it is, your signature validates fine but this header bit turns up before the signed message part. This seems to suggest the enigmail extension is causing Thunderbird to discard or ignore this part of the header for some reason (One of your earlier messages was immediately available for checking, and as I know you are also not a Thunderbird user it was rather handy for narrowing things down, otherwise I would need to configure Evolution or KMail for signing for further testing :-) ).
part of the header appears in the body of the message on my machine. I have checked the enigmail bugzilla and it has not been reported there. I know the SuSE build is slightly different from the Mozilla release, so it is possibly a SuSE thing. Can anyone else confirm this behaviour. It is not a major issue as far as I can work out, but I have spent rather more time on working out what is going on than I would have preferred.
Sorry. I have known this for a bit more than a week, but I didn't though of reporting it to bugzilla, not knowing if it is a Novell issue. I commented this to the developper of the gpg filter I use, in the Alpine email list.
This is what I am attempting to establish.. if anyone is seeing this on a non SuSE version of Thunderbird or not ... In searching for references about the problem I came across security references associated with Content-Type and I rather wondering whether we are getting some sort of interaction between a Novell specific patch and enigmail... I could test with windows but I am not certain this would be valid as the Windows version of the enigmail extension seems to be a bit less featured (and I would have to configure it).... It is more of a nuisance than anything else...
-- Cheers, Carlos E. R.
- -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHdPj/asN0sSnLmgIRAkx0AJ9jD0qhd62avDyp50soYZZxw8hzUQCcDgn+ f/3NY1dKQdj1HjM7cE6ELVA= =c2LG -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org