https://bugs.kde.org/show_bug.cgi?id=374546
Sandro Knauß <skna...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |skna...@kde.org
--- Comment #12 from Sandro Knauß <skna...@kde.org> ---
The root of the problem is that kmail is using "binary sigantures" sigclass
0x00 and not "text signatures" sigclass 0x01. And binary signatures do not
allow changes in lineend aka \n -> \r\n text signatures allow these and strip
empty lines at the end
Nearly all MUAs expect, that the signatures are "text signatures" and do not
take care about these little changes. See also:
http://www.openpgp-schulungen.de/info/verify-mime/ (german link)
IMO kmail should also switch to "text signatures" because for email it is only
text and all binaries need to be encoded to BASE64. Unfortunately RFC3156
allows both. But still tells a exact way to prepare the signature (section 5).
Also rfc4880 can be interfering here (section 7 and 7.1) that request
modifications before signing it. In my experience other MUAs modifies the
content because they need to push the content through the cmdline instead using
gpgme, that's why the signature fails.
--
You are receiving this mail because:
You are watching all bug changes.
