Breaking MIME concatenation
martin at postzone.org
Wed May 16 15:46:05 CEST 2018
-----BEGIN PGP SIGNED MESSAGE-----
Am Dienstag, 15. Mai 2018, 22:19:17 schreiben Sie:
> On 05/15/2018 04:44 AM, Patrick Brunschwig wrote:
>> I think the correct solution must be to treat each MIME part
>> independently, i.e. it needs to be parsed independently by the HTML
>> engine and produce its own DOM tree. At the end, you can concatenate
>> these DOM trees and create a single correct HTML document.
> So why use HTML with gnupg?
I think a fundamental discussion is necessary with the question: Who
should / will use GnuPG in the future?
Two extremes: Only these people who need really to encrypt their
emails because they are persecuted. But these people learned how to
handle their email client correctly and these people will write
text-only also in the future.
Or is Email encrypting a need for *every* email user? But there the
standard today IS that mails are HTML-written and contain links and
pictures and so on. If GnuPG should be a tool for "everybody" HTML
mail must be encrypted and decrypted correctly by the clients and
GnuPG should give any important information,
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
More information about the Gnupg-users