Protected headers (memoryhole) not recognized by Thunderbird
Hi. Firstly thank you for developing this project and adding protected headers support. Secondly, a disclaimer. I haven't read nor understood the RFC of protected headers, so my issue might not be 100% accurate. Nevertheless the problem exists somewhere.
Protected headers sent by mutt look like this:
Content-Type: text/plain; protected-headers=v1; charset=utf-8
Content-Disposition: inline
Date: Sat, 23 Jan 2021 12:13:24 +0100
From: John Doe <from@example.com>
To: to@example.com
Subject: Encrypted Subject
Encrypted Content
Minimal payload understood by Thunderbird (78.6.0) is:
Content-Type: text/plain; boundary="Ky3CPrsjupuae9cZqYwIeBOHvjkpPNGuP";
protected-headers="v1"
Subject: Encrypted subject
From: John Doe <from@example.com>
To: to@example.com
Message-ID: <probablynotimportant>
--Ky3CPrsjupuae9cZqYwIeBOHvjkpPNGuP
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
Encrypted data
--Ky3CPrsjupuae9cZqYwIeBOHvjkpPNGuP--
otherwise TB shows "..." in the subject.
To sum up: mutt's protected headers are understood by mutt but not Thunderbird (the subject is "..."). TB's protected headers are understood by mutt and Thunderbird.
https://www.ietf.org/archive/id/draft-autocrypt-lamps-protected-headers-02.txt This is about some "Legacy" algorithm, I don't know what is the new one, but I'm kind of focusing on Thunderbird being usable with crypto (with their new PGP support things are going almost great).
The Cryptographic Payload must have a "Content-Type" of
"multipart/mixed"The Cryptographic Payload must have exactly two subparts
The first subpart of the Cryptographic Payload must have a
"Content-Type" of "text/plain" or "text/rfc822-headers"The first subpart of the Cryptographic Payload's "Content-Type"
must contain a property of "protected-headers", and its value must
be "v1".
Please tell me if that's a bug in mutt or not, I'll be happy to test the patches. Thank you!