this post was submitted on 14 Sep 2023
28 points (100.0% liked)
Technology
59148 readers
2280 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Err how is mail E2E encrypted when mail isn't typically E2E encrypted? It has to reach a mailbox. If that mailbox isn't on your computer, then it's on Proton's.
That's why you need to install the proton mail bridge if you want to use it with apps like thunderbird. Of course, Emails not send from or too another proton account are not encrypted, but that's something proton can't change... Although you can put a password on your emails, so only people who know that password can access the mail, but that's more of a workaround than a fix.
I'm not a proton employee, so I can't give you the exact process used, but basically Protonmail probably uses asymmetrical encryption to encrypt incoming emails as soon as they receive it.
Asymmetrical encryption uses two keys. A public one, and a private one, both linked together by two one-way mathematical function. The public one can be used by anyone to encrypt a message using said one-way function, but cannot be decrypted without using the private key, which is itself encrypted by your password (which is both unknown to Proton, that why you cannot recover your data if you forget your password), and probably other parameters like your main Protonmail email address.
Now, on the client side, your password (and any other parameters) are used to locally decrypt the private key, which in return is used to locally decrypt the data send by Protonmail servers.
Sure, it isn't true E2E encryption, but it is the closest to it you can get while talking with another server that do not support E2E encryption.
But there is more. If you send an email to another Protonmail client, said email will be truly E2E encrypted as both client will have access to each other public key, allowing them to encrypt the message on the client side, which will prevent Protonmail from ever read it. If I'm not mistaken, sames goes with any PGP enabled client (like Thunderbird with the Enigmail addon).
Right. So they could store them encrypted this way but they still have the opportunity to copy them at the intake point as you suggest. All of this make sense and I agree it's probably the closest you can get to E2E with email without employing some OTG encryption that both sender and receiver participate in. Thanks for the musings!