If you were to somehow encrypt the subject and send the email, how would
you propose the recipient decrypts it?
Email subject line encryption just isn't a feature of PGP, per RFC
4880. Even if Mutt could do it, chances are very slim the client on the
other end would be able to decrypt it (I'm not aware of any that do
this, though some may exist using proprietary solutions), and then
there's the problem of multiple recipients, which could result in a very
large subject field, which in itself could break delivery agents and
mail clients.
On 11/7/2011 4:44 AM, P. Mazart wrote:
Hi Patrick,
thank you for your answer!
Patrick Shanahan schrieb am 07.11.2011 13:21:37:
an encrypted Subject would only be visible to the intended recipient
holdiong the correct key and only after he decrypted the post, so what
would be the point?
Avoiding inference about the email’s content…
That’s why we use pgp, don’t we‽
Why would you send an encrypted post (?Subject) to
anyone but the intended recipient?
I guess we got each other wrong here,
I was indeed talking about encrypting AND sending
to the keyholder.
None the less I stick to the policy of choosing a
proper, content describing, subject which in return
does reveal information about the content while traveling
over the net.
So a dummy subject which might be overridden after the first
decryption might fit the purpose of “hiding” information about the mail…
I wonder if there’s some ideas on that yet.
Thank you.
P.M.
