You are viewing a single thread.
View all comments View context
1 point

Because we only know what the client does, and have no clue on the server side of things, allowing Proton to do any manipulations with the data. Not ideal when you consider it for password storage.

permalink
report
parent
reply
1 point

What should I use then?

permalink
report
parent
reply
1 point

Something like Vaultwarden if you care about cloud sync, or KeePassXC if that’s not on your priority list.

permalink
report
parent
reply
1 point

if the client is e2ee and you can control that, then why is the server relevant?

permalink
report
parent
reply
1 point
*

Because non-obvious backdoors can be added to the client that break or circumvent encryption (looking at you, xz), stealing all of your passwords, and no one will be able to raise the alarm just by looking at the server code.

Open-source backend allows to generally avoid this situation, while also potentially rendering you able to self-host if you’re paranoid.

permalink
report
parent
reply
1 point

and you can control that

Sorry, I meant “assuming one has complete control over the client source” where the remote cannot just change it on you.

permalink
report
parent
reply

Open Source

!opensource@lemmy.ml

Create post

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

  • Posts must be relevant to the open source ideology
  • No NSFW content
  • No hate speech, bigotry, etc

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

Community stats

  • 3.6K

    Monthly active users

  • 1.8K

    Posts

  • 30K

    Comments