Skip to content
This repository has been archived by the owner on Jun 24, 2022. It is now read-only.

"Built-in Encryption" not clear #1706

Closed
desk7 opened this issue Feb 12, 2020 · 1 comment
Closed

"Built-in Encryption" not clear #1706

desk7 opened this issue Feb 12, 2020 · 1 comment

Comments

@desk7
Copy link

desk7 commented Feb 12, 2020

In Privacy-Conscious Email Providers what does "Built-in Encryption" actually mean? That the email are sent encrypted (TLS) or that they are zero-knowledge encrypted?
I thought the second option but then I see that for example in disroot.org "All emails, unless encrypted by user (with gpg for example) are stored on our servers in plain-text."
Tutanota and protonmail, for example, implement E2E encryption instead. The difference is huge and not evident from the table.

So, please make clearer the meaning of "built-in encryption" or remove the providers that doesn't offer E2E encryption.

Thanks

@danarel
Copy link
Contributor

danarel commented Feb 12, 2020

We are re-doing the entire email section which can be seen at #1672 which will make items like this more clear and better define email providers we recommend.

@danarel danarel closed this as completed Feb 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants