• Gimpydude@lemmynsfw.com
    link
    fedilink
    English
    arrow-up
    31
    arrow-down
    2
    ·
    9 months ago

    Meta could easily have the WhatsApp client upload decryption keys to their servers without any notification to the user.

    • Flumpkin@slrpnk.net
      link
      fedilink
      English
      arrow-up
      14
      arrow-down
      1
      ·
      9 months ago

      Not sure what you mean, of course WhatsApp can disable it’s own encryption. That would be an argument for open source third party apps and interoperability.

      • Gimpydude@lemmynsfw.com
        link
        fedilink
        English
        arrow-up
        3
        ·
        9 months ago

        What I’m talking about has nothing to do with the line protocol. Each client has encryption key pairs. The public key of the first party shares it with the other parties, and vice versa. If it’s encrypted with the public key then the private key can decrypt it.

        If Meta gets the private keys, they can decrypt any message they want independent of whatever protocol is being used.

        • Flumpkin@slrpnk.net
          link
          fedilink
          English
          arrow-up
          4
          ·
          9 months ago

          But aren’t these key pairs generated per session and/or per contact? So once you switch to a more secure / auditable client this only matters when communicating with people on whatsapp. But they presumably have a backdoor in their app for the NSA anyway.

    • federal_explorer
      link
      fedilink
      English
      arrow-up
      1
      ·
      9 months ago

      No body said it’s going to have the same level of security, but that still doesn’t mean that should just give up on it, just put a small icon indicating this is a WhatsApp user.