Trace:

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
lacre:ongoing [2024/07/12 14:51] – add: Thunderbird's handling of single-part messages pfmlacre:ongoing [2024/07/12 17:17] (current) – cont: Research: Thunderbird's handling pfm
Line 48: Line 48:
   * If the user chooses to sign the message, their public key is included in the ''multipart/mixed'' entity.   * If the user chooses to sign the message, their public key is included in the ''multipart/mixed'' entity.
   * Actual message body is included as Base 64-encoded MIME part of the ''multipart/mixed'' entity.   * Actual message body is included as Base 64-encoded MIME part of the ''multipart/mixed'' entity.
 +
 +Unfortunately we need to compose new MIME entity for every PGP/MIME-encrypted message, so we need to load contents of each part. To avoid transformation we could switch from ''get_content()'' to ''get_payload(decode=False)'', so we'd get strings with raw MIME entity payloads, giving us a chance to populate ''multipart/mixed'' in step 2 above with non-transformed payloads.