Well that didn’t take long…
• Beeper, the company behind iMessage for Android, faces an outage after Apple cuts off its access.
• The highly anticipated service, which brought blue bubble texts to Android, may have violated Apple’s terms of service.
• Beeper’s access to iMessage was revoked soon after its launch, raising questions about the feasibility of the service.
Isn’t it surprising how nobody’s raised to stink about iOS having poor message encryption? Their white paper has been around for at least 5 years at this point, but I guess most of us shrugged and just decided it was good enough.
Makes you wonder about all the other stuff they’ve made E2EE more recently, and how unlikely it is that it’s much better. Messaging is one thing, file encryption is more static.
Not sure I would call it poor encryption. As yet, no one’s cracked that large of an RSA key.
I’d certainly call it less than advertised, and needing some updates like increase the RSA key, separate the encrypted message from the AES key, and use other mechanisms so it doesn’t have a single point if failure (the RSA key).
They also need to change the identifiers, since that has a risk of MITM attacks.
But yea, they’ve had 4 or 5 years and done nothing. That’s BAD.