• MrSpArkle@lemmy.ca
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    39
    ·
    7 months ago

    How would a third party client guarantee e2e encryption with iMessage?

    And by what mechanism was that company enabling that bridge? Did that mechanism store iCloud credentials? Did it encrypt the drives the users iCloud data could have been downloaded to? Did they have access to iMessages in clear text before forwarding them?

    • ferralcat@monyet.cc
      link
      fedilink
      English
      arrow-up
      29
      arrow-down
      1
      ·
      7 months ago

      The entire web is built on standardized e2e encryption schemes fought for by techie nerds so that we don’t have these problems there.

    • ReallyActuallyFrankenstein@lemmynsfw.com
      link
      fedilink
      English
      arrow-up
      15
      arrow-down
      3
      ·
      7 months ago

      I’m not a programmer, but this doesn’t seem hard. The API could specify a cryptographic standard. Third party clients don’t need access to iCloud data, just the API to pass message and attachment content in encrypted form with a standardized handshake.

      What am I missing?