https://bugs.kde.org/show_bug.cgi?id=399055
--- Comment #1 from Jan Kundrát <[email protected]> --- Hi Jens, thanks for this report, I think that you have identified a scenario which we missed. This looks like a valid concern to me. It would be reasonably straightforward to move the indication outside of the body/part content area if the entity being signed/decrypted is a top-level multipart. However, it is harder to do so when the signed/encrypted item is a MIME part which is nested deeper into the MIME tree. I.e., our initial design was motivated by willing to support a scenario where someone forwards a signed e-mail, so that the tree looks like this: root: multipart/mixed | +-- text/plain saying "Hi, plesae check this message from Bob" +-- message/rfc822, the original Bob's message | * +-- multipart/signed, a correct signature from Bob * | * +-- text/plain or whatever else with Bob's message * +-- the signature data ^--- these stars indicate what is actually signed, and what the UI shows as signed Do you have a suggestion on how to tackle this? Yes, "perfect is an enemy of good" and such, but still I think that we should not be degrading e-mails into "whatever can be produced by today's webmails". MIME is a pretty reasonable data abstraction, and my preference is to support that if at all possible. Do you see a way here? -- You are receiving this mail because: You are watching all bug changes.
