mirror of
https://github.com/anonaddy/anonaddy.git
synced 2026-04-25 14:15:53 +03:00
[GH-ISSUE #243] (feature request) memoryhole support #215
Labels
No labels
bug
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/anonaddy#215
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @bruceleerabbit on GitHub (Dec 24, 2021).
Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/243
It’s great that payloads are PGP-encrypted, but what about the headers? IIRC, there is a standard or convention called “Memoryhole” which specifies a way to embed all the headers inside the PGP-encrypted payload, so that the only essential header (the recipient’s email address) is exposed. IIRC Thunderbird has memoryhole support.
Would be a great evolution since anonaddy already supports PGP. It would be a big privacy gain for users of GAFAM email (e.g. Gmail, Hotmail, Outlook), since those privacy abusers exploit the metadata for all it’s worth as it is.
@willbrowningme commented on GitHub (Jan 12, 2022):
I wasn't aware of this so thanks for the suggestion. I'm assuming this site is the best place for documentation on this feature? I'll look into this in more detail when I get time.
@bruceleerabbit commented on GitHub (Jan 21, 2022):
Hmm… That's a Cloudflare site which serves as a credibility problem for the maintainers. But if that’s where the needed info is, it may be indispensible.
I should also point out that S/MIME seems to have a competing standard for the same purpose so that may be worth a look. There’s more discussion in this thread about adding Memoryhole to Neomutt→ https://github.com/neomutt/neomutt/issues/741
@willbrowningme commented on GitHub (Nov 1, 2022):
Protected headers has now been added that allows the subject to be hidden and encrypted in the message body and replaced with "...". You can enable this for each individual recipient from the recipients page.