Today we’re announcing a new end-to-end encrypted, collaborative document editor that puts your privacy first. Docs in Proton Drive are built on the same privacy and security principles as all our services, starting with end-to-end encryption. Docs let you collaborate in real time, leave comments, add photos, and store your files securely. Best of all, it’s all private — even keystrokes and cursor movements are encrypted.
Literally the second paragraph of the post (but I’m sure you haven’t read it, since you seem so busy replying to every comment here about how Proton is becoming Microsoft or something).
So sending a company your private key and trusting their servers to do E2E encryption despite them being able to modify their code whenever they feel like it to capture your password without encryption and masked in obfuscated JavaScript is now considered security? Wow, people really are gullible.
I agree with your general sentiment here (that such an arrangement is not trustworthy enough for me to feel completely private) but your delivery of said sentiment is really fucking rude, dude.
Even if it’s not secure enough for you or I to feel private, it likely exceeds the security necessary to satisfy most people’s threat models so they can not only feel private but objectively be more private than if they just used Google docs.
incremental or opportunistic privacy improvements are better than none, a fact that has seemed to be lost in elitist privacy circles these days.
I’m not sure what you’re talking about ?
You’re not sending your private key to their server without first encrypting it first locally.
Their server are not doing the E2EE, your client is.
The website front and apps are open source.
Yes they could send you a compromised front if you use it via their website, that’s a compromise you accept, otherwhise you could only use their apps which are open source.
Tell me… when you visit a website that gets updated daily, if not hourly. If it served you a different version of JavaScript than what it served someone else… would you know?
micka190@lemmy.world 2 months ago
Literally the second paragraph of the post (but I’m sure you haven’t read it, since you seem so busy replying to every comment here about how Proton is becoming Microsoft or something).
timewarp@lemmy.world 2 months ago
So sending a company your private key and trusting their servers to do E2E encryption despite them being able to modify their code whenever they feel like it to capture your password without encryption and masked in obfuscated JavaScript is now considered security? Wow, people really are gullible.
experbia@lemmy.world 2 months ago
I agree with your general sentiment here (that such an arrangement is not trustworthy enough for me to feel completely private) but your delivery of said sentiment is really fucking rude, dude.
Even if it’s not secure enough for you or I to feel private, it likely exceeds the security necessary to satisfy most people’s threat models so they can not only feel private but objectively be more private than if they just used Google docs.
incremental or opportunistic privacy improvements are better than none, a fact that has seemed to be lost in elitist privacy circles these days.
asdfasdfasdf@lemmy.world 2 months ago
He’s wrong about what he said, too. You do not send Proton your private key.
timewarp@lemmy.world 2 months ago
Incremental in what way? There is an illusion of privacy. If that makes people feel good then sure, you increase your illusion of privacy.
brochard@lemmy.world 2 months ago
I’m not sure what you’re talking about ? You’re not sending your private key to their server without first encrypting it first locally. Their server are not doing the E2EE, your client is. The website front and apps are open source.
Yes they could send you a compromised front if you use it via their website, that’s a compromise you accept, otherwhise you could only use their apps which are open source.
timewarp@lemmy.world 2 months ago
Tell me… when you visit a website that gets updated daily, if not hourly. If it served you a different version of JavaScript than what it served someone else… would you know?