• asudox@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    11
    ·
    edit-2
    6 months ago

    This is old news. Why are you posting this just now? I mean I don’t really care much. I transitioned to Posteo as soon as I learned that they stored the private key. They don’t even let you use your own GPG key, useless honeypot. Their recent bitcoin wallet supports this. If they cared about privacy, they wouldn’t go with Bitcoin. They have been ignoring requests for monero since years.

    They also are getting into the AI hype, so I can’t trust my data with them.

    • sudneo@lemm.ee
      link
      fedilink
      English
      arrow-up
      9
      arrow-down
      1
      ·
      6 months ago

      You can use your own GPG key (https://proton.me/support/importing-openpgp-private-key or using the bridge), whatever tool does the signing needs the key (duh) so I am not sure what you mean by “they store your private key” (they stored it encrypted as per documentation https://proton.me/support/how-is-the-private-key-stored), their AI was specifically designed as local, exactly to be privacy friendly, plus is a feature that can be disabled (when it will reach general subscriptions).

      I don’t care about cyptocurrencies, but I suppose they started with the most popular, nothing to do with privacy as they just let you store your currencies.

      Anyway, use what you like the most, of course, but yours don’t look very solid motivations, quite a lot of incorrect information, I hope you didn’t take your decision based on it.

      • asudox@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        1
        ·
        edit-2
        6 months ago

        You upload your private key to the cloud. Encrypted or not, this is a bad idea. No thanks. I can do the signing locally and then I’ll do the decryption with my own private key locally without them storing it as well.

        Edit: mixed public keys with private keys

        • sudneo@lemm.ee
          link
          fedilink
          English
          arrow-up
          6
          ·
          6 months ago

          You upload your private key to the cloud. Encrypted or not, this is a bad idea.

          An encrypted key is a useless blob. What matters is the decryption key for that key, which is your password (or a key derived from it, I assume), which is client side.

          They can do the signing and encryption with my public key

          They can’t sign with your public key. Signing is done using your private one, otherwise nobody can verify the signature.

          Either way:

          and then I’ll do the decryption with my own private key locally without them storing it.

          You can do it using the bridge, exactly like you would with any client-side tooling.

    • Midnight Wolf@lemmy.world
      link
      fedilink
      English
      arrow-up
      4
      ·
      6 months ago

      This is old

      “I know this. Why doesn’t everyone else know this? They should be me, I’m the smartest man alive.”

      I really don’t care much

      proceeds to type an entire paragraph as to why you don’t care