• @[email protected]
    link
    fedilink
    125 days ago

    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.

    • @Sgn
      link
      125 days ago

      What should I use then?

    • @refalo
      link
      123 days ago

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

      • @[email protected]
        link
        fedilink
        1
        edit-2
        22 days ago

        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.

        • @refalo
          link
          122 days ago

          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.

          • @[email protected]
            link
            fedilink
            2
            edit-2
            22 days ago

            I mean they can make a sneaky update to the client that introduces such changes.

            Sure, if you won’t update your client, this won’t affect you, but would potentially open you up to other security vulnerabilities.

            • @refalo
              link
              2
              edit-2
              22 days ago

              This was a real concern with MEGA back in the day (after Kim said you should no longer trust them) and a big reason why I prefer to use standalone client apps that I can control the source of.