broken charset/encoding autodetection for encrypted messages
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mozilla Thunderbird |
New
|
Unknown
|
|||
kdepim (Debian) |
Fix Released
|
Unknown
|
|||
thunderbird (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Version: 1:31.0+
Hi,
this is a bug Mozilla™ Thunderbird and KDEPIM share:
When I send an Inline PGP encrypted message, whose body is using UTF-8, to another user, the message is ASCII armoured (and thus 7bit). The other user, running Thunderbird or Kontact, (or my own Kontact instance in the “sent-mail” folder), gets the message and interprets the post-decryption body as ISO-8859-1 (or Windows-1252, probably) instead of UTF-8.
Manually switching the encoding to Unicode in the menu corrects this… for this one message. (See https:/
The problem here is that the human message encoding (everything within the PGP armour) must be separated from the transport message encoding (the RFC822 message in which the “-----BEGIN PGP MESSAGE”…“END PGP MESSAGE-----” is transmitted) must be separated from each other, which they aren’t.
Please fix this, it harms using those MUAs in an enterprise environment.
Changed in kdepim (Debian): | |
status: | Unknown → New |
Changed in thunderbird: | |
importance: | Unknown → Medium |
status: | Unknown → New |
Changed in kdepim (Debian): | |
status: | New → Confirmed |
Changed in kdepim (Debian): | |
status: | Confirmed → Fix Released |
Changed in thunderbird: | |
importance: | Medium → Unknown |
User Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 (Beta/Release)
Build ID: 20140717132905
Steps to reproduce:
The Thunderbird user received an Inline PGP encrypted eMail from me. The content of that was UTF-8 encoded; the transport message body contained an ASCII-armoured PGP message.
Actual results:
The Thunderbird user got the message interpreted as ISO-8859-1 or Windows-1252, instead of UTF-8. This was also reported as: https:/ /bugs.launchpad .net/ubuntu/ +source/ thunderbird/ +bug/1357227
This means the automatic detection of UTF-8 is broken, and/or the encoding of the RFC822 transport container is mixed up with the encoding of the message.
Manually selecting Unicode from the message encoding menu, the message is displayed correctly. Switching away from the message and back to it causes the setting to reset; this was also reported as: https:/ /bugs.launchpad .net/ubuntu/ +source/ thunderbird/ +bug/1108980
Expected results:
The user should have seen the Unicode characters in the message correctly, instead of mojibake.