Combine the content-type handlers for OpenPGP and S/MIME into a single one
Categories
(MailNews Core :: Security: OpenPGP, enhancement)
Tracking
(Not tracked)
People
(Reporter: KaiE, Unassigned)
References
Details
This an architectural enhancement suggestion.
For historical reasons, the handling code for the multipart/signed content-type is split into two separate pieces of code, a C++ portion that handles S/MIME, and a JavaScript portion that handles the OpenPGP code.
If the currently registered handler is the wrong one for the message being processed, a hack is used to dynamically change the registered handler. That's inefficient, because it requires that the message is loaded again, and it also leads to wrong functionality, for example as seen in bug 1946168.
We should have only one handler, and avoid reloading and re-registering.
Instead, the one handler should simply forward to the correct piece of code for data processing.
(This would also prepare for a future in which we might have to handle additional protocols.)
|
||
Comment 1•10 months ago
|
||
This would be great!
Description
•