https://bugs.kde.org/show_bug.cgi?id=248058
Andre Heinecke <aheine...@intevation.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |aheine...@intevation.de
--- Comment #7 from Andre Heinecke <aheine...@intevation.de> ---
> PGP Inline is perfectly fine standardised: the display agent has to use the
> charset indicated by the PGP
> message, and discard any charset/encoding information of the surrounding
> message.
No it's not. Especially the Encoding handling is very problematic and not
standardised. See: https://debian-administration.org/users/dkg/weblog/108 (
https://dkg.fifthhorseman.net/notes/inline-pgp-harmful/ )
Basically your Mail says that it's ASCII Encoded but then actually has UTF-8
encoding in the content after decryption. I would argue that this is not a
KMail bug but that your Mail is broken. For proper encoding Handling you need
to use PGP/MIME. One of the Advantages of PGP/MIME is proper encoding handling.
KMail uses the Content-Type charset of the PGP Message which would be correct.
GnuPG / GPGME itself does not do any reencoding it just decrypts the "bytes" of
the message.
The Armor Header from RFC2440 is afaik not used in practice. As changing the
encoding can change the meaning and the armor headers themself are not signed /
encrypted this offers not much advantage over the Content-Type.
Except that you would have an even more fragile implementation because you
would have to handle mixed encodings in a message for multiple PGP/Message
parts. And you would have to treat PGP Clearsigned messages differently,..
As a "workaround" / to improve compatibility with broken MUA's I like Sandro's
idea to treat PGP Messages as UTF-8 if the specified Charset is 7Bit ASCII. I
think that would be a good solution to fix your bug.
Although I would suggest to use a proper MUA with PGP/MIME support.
--
You are receiving this mail because:
You are watching all bug changes.
