-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 9/10/2016 4:00 PM, Robert J. Hansen wrote: >> I'm confused by this. What does it mean? What does 'armor the >> mail headers" mean? Is this the same as 'encrypting' the mail >> headers or does it mean something else? > > It means there's a way to cryptographically protect most (but not > all) email headers, which foils many kinds of metadata analysis. > > At present I don't think any email client supports this > capability. However, it's planned for Enigmail and other clients, > and it's a good reason to use PGP/MIME instead of inline.
Hmm, OK that's kind of what I thought. But I'm still a little confused. Doesn't the email server have to support it? For example, if I send an email to someone using Gmail, how does Gmail route it if the headers are encrypted? Or would the "to" be one of those things not encrypted? Anthony -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJX1HjfAAoJEAKK33RTsEsVHi0P/3pvxxom79zB0C3HjRXsuGiD Lkic5Q6ZTlU8T6OHW82eg30tx6sduss8WSdJqtaLBkY+ob2aIPFW6sP+sekYCjDd Y6k8dmRZmq7M0obt7MCOy+GN54PtUXl49JIUA9969NuayRD6nLmrBmUOTi/2Alup Z+IgjkWo7PIoSo1nJW8r9iEaEQIRix7l0Lv+7+mI0mLfoBfuvfeTYeQYVvS4Xy9X ldwbgf04lu3FQUEPAdu5OHXiNHzNbtq96g+Z9TovUHS3rlpM0vdAnSS0tf+V1l1W Z+KRDx3tQZD2Dh6DZpaPuyuZQt2pbaHT1DqBWx4FdIhY6EIzMu02xwJLL5MZDAlb N2FLO8S/98Ruzk4Oo4rxCFHviIwd9SVIr81ZDIeGUNvz3xvAxKs9M4cABPTc0T94 oM5sa6DWnWw8omKuy3aDNFoozL8qICf1GSLKtcmns97SuhGquJxTDTEkHykBuDIt GWev2+QCha7fQSPInSO71jtH32YANpitEjW6HMrZzcC6QPOMQrNeKxu2BKs77UUm ai/0hPGtmEW4AO/N3h4lyi6jqSZVtNQvtZjvE0S8VTdSDFCTAcfRlxRJOFbCC7ir /mkhX+aAmdIQ7rRbAW3u8+C8kp0cstsLJ+pdjVGr++edsaDCktveEvJa2IBxubgM vI23TVNvR0OZJosgdgmG =JGbA -----END PGP SIGNATURE----- _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users