https://bugs.kde.org/show_bug.cgi?id=286553
Sandro Knauß <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #23 from Sandro Knauß <[email protected]> --- Thx for these informations. Now I can reproduce this behaviour and understand, what's going on. I can confirm also that the signature is correct by using gpg --verifiy signature.sig text.txt This bug can be viewed differently. Either we can say, this is a bug of enigmail (extensions/enigmail/package/mimeVerify.jsm line 184): this.writeToPipe(data.replace(/^-/gm, "- -")); They modify the signed message, that should never ever be done. Like RFC 3156 says: "Multipart/signed and multipart/encrypted are to be treated by agents as opaque, meaning that the data is not to be altered in any way" The other way we can look atthis bug, is that we ignoring RfC 3156 recommendation: "It cannot be stressed enough that applications using this standard follow MIME's suggestion that you 'be conservative in what you generate, and liberal in what you accept.' " To solve this bug kmail has to use Quoted-Printiable or Base64 and escape the signature sequence "--\n", that causes enigmail to change the content of the signed content.t -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list [email protected] https://mail.kde.org/mailman/listinfo/kdepim-bugs
