Conform to p≡p standards and encrypt headers #3

New issue

Open

opened 2024-11-06 23:12:24 +00:00 by revsuine · 1 comment

revsuine commented

2024-11-06 23:12:24 +00:00

Owner

https://datatracker.ietf.org/doc/html/draft-marques-pep-email-02

https://blog.jak-linux.org/2019/06/13/encrypted-email-storage/

Now, we almost have a file conforming to draft-marques-pep-email-02. That format allows us to encrypt headers, thus preventing people from snooping on our metadata!

Basically it relies on the fact that we have all the headers in the inner (encrypted) message. To mark an email as conforming to that format we just have to set the subject to p≡p and add a header describing the format version:
   Subject: =?utf-8?Q?p=E2=89=A1p?=
   X-Pep-Version: 2.0
A client conforming to p≡p will, when seeing this email, read any headers from the inner (encrypted) message.

We also might want to change the code to only copy a limited amount of headers, instead of basically every header, but I’m going to leave that as an exercise for the reader.

https://datatracker.ietf.org/doc/html/draft-marques-pep-email-02 https://blog.jak-linux.org/2019/06/13/encrypted-email-storage/ > Now, we _almost_ have a file conforming to [draft-marques-pep-email-02](https://tools.ietf.org/html/draft-marques-pep-email-02). That format allows us to encrypt headers, thus preventing people from snooping on our metadata! > > Basically it relies on the fact that we have all the headers in the inner (encrypted) message. To mark an email as conforming to that format we just have to set the subject to p≡p and add a header describing the format version: > > Subject: =?utf-8?Q?p=E2=89=A1p?= > X-Pep-Version: 2.0 > > A client conforming to p≡p will, when seeing this email, read any headers from the inner (encrypted) message. > > We also might want to change the code to only copy a limited amount of headers, instead of basically every header, but I’m going to leave that as an exercise for the reader.