• n2burns@lemmy.ca
      link
      fedilink
      arrow-up
      4
      ·
      1 year ago

      Would it not be E2EE? Isn’t that one of the reasons for using the Signal protocol?

      • muhyb@programming.dev
        link
        fedilink
        arrow-up
        10
        ·
        1 year ago

        Yes, the “delivering” part would be E2EE. Do we really know the afterwards if they can read their users’ messages? They probably can.

        • falsemirror@beehaw.org
          link
          fedilink
          arrow-up
          9
          ·
          1 year ago

          Whatsapp CANNOT read messages when e2ee is enabled, this client-side snooping was discussed when the protocol was first implemented. Whatsapp collects a ton of metadata and social graph info, but not message content.

          • blackstrat@lemmy.fwgx.uk
            link
            fedilink
            arrow-up
            4
            ·
            1 year ago

            Well you type messages in in plain text and they decrypt it to show you the messages at the other end. So they can do the nefarious processing on the client side and send back results to the mother ship. E2EE is only good when you trust the two ends, but with WhatsApp and Messenger you shouldn’t trust the ends.

        • n2burns@lemmy.ca
          link
          fedilink
          arrow-up
          4
          ·
          1 year ago

          Sure, but any messaging app (including Signal) could have these backdoors in place. Heck, there’s even vectors for unrelated apps on your phone to read this data once unencrypted.

      • authorinthedark@lemmy.sdf.org
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 year ago

        if i remember correctly, it would be E2EE (WhatsApp and Messenger are too) but Meta stores the encrypted message on their server