Decrypt email and view source (Thunderbird)
Categories
(MailNews Core :: MIME, enhancement)
Tracking
(Not tracked)
People
(Reporter: KaiE, Unassigned)
References
Details
In addition to the existing "view source" for email messages,
I suggest to add a mechanism that allows to "view decrypted source".
That is, if an email is encrypted, it should be decrypted, and the resulting message source should be shown in a view source window.
This would allow easy viewing of the inner content type, and the encrypted "protected headers".
Maybe this isn't much work, we just need to understand how to use the MIME decoders to decrypt the message, prior to sending it to the view source code?
|
||
Comment 1•6 years ago
|
||
Good suggestion. What I'd like to see happening for "view source" would also be to decode base64-encoded parts.
It would be nice if this were implemented in a way that our pEp add-on could also use the functionality, that is, via the PGP Proxy.
|
Reporter | |
Comment 4•4 years ago
|
||
User nilsirl just pointed me to "file save as", and the option to select the file type there.
When selecting "text" or "html" as the file type, the resulting file has some decrypted contents (minus the attachments). I wasn't aware we have that.
However, the file we produce isn't the original message. It's the result of preparing the visual display of the encrypted message, which excludes the attachments.
While this may be helpful for some limited debugging, this isn't what this ticket requests us to.
Also, the behavior I describe in this comment is limited to messages of the PGP/MIME format. For "pgp inline" messages, the file doesn't have decrypted contents. The reason is that "pgp inline" messages are treated differently, and use a two step approach. (We being by showing the message, then detect the contents, then replace the visual display).
This means:
-
we still need a fix for the original request
-
it might be useful to clarify the user interface, and explain what exactly the current "file save as" feature does
|
|
Reporter | |
Comment 5•4 years ago
|
||
I think we no longer need to fix this bug.
The functionality implemented in bug 1693332 can be used to obtain the decrypted version of a message.
Description
•