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?
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.
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?
The entire web is built on standardized e2e encryption schemes fought for by techie nerds so that we don’t have these problems there.
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?
And what data would this client be handling via the API?
Even Signal discourages third party apps for this reason you are indeed missing.
Signal is open source. That’s why they warn against using third party closed source apps which cannot be security audited.
iMessage is a proprietary app that cannot be security audited. An open source alternative would be more secure, not less.