encrypting the headers will not stop traffic analysis and can be confusing to some of us .    i think it is much better to simply suggest using an innocuous subject line placing any critical information into the body of the message.    i.e. the whole question my be a matter of technique more than a programming need .

On 09/17/2015 03:09 AM, Daniel Kahn Gillmor wrote:
On Thu 2015-09-17 02:30:14 -0400, Patrick Brunschwig wrote:
On 17.09.15 02:55, Ian Mann wrote:
http://sourceforge.net/p/enigmail/wiki/Planning%20for%20version%201.9/

How do we turn on support for encrypted subject and other headers
in the nightly build of V1.9

support encrypted subject and other headers [[Done]]
Short answer: don't do it yet. The plan is that V1.9 will have all
capabilities to encrypt and decrypt the headers, but the functionality
will be off by default. The version following V1.9 will enable the
feature, possibly even unconditionally.

The reason for this is that we first need to ensure that the majority
of the users can handle decryption of headers before we can start
encrypting them.
More precisely: we should be able to put headers inside the encrypted
messages soon, but we don't want to strip or stub-out the non-encrypted
headers *outside* the encrypted messages until we know that the messages
are readable by other users.

You should be able to generate signed headers (and to verify that the
headers are signed) before you start seeing headers that are actually
protected by encryption.

       --dkg

_______________________________________________
enigmail-users mailing list
[email protected]
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net

-- 
/Mike
_______________________________________________
enigmail-users mailing list
[email protected]
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net

Reply via email to