They didn't really "crack" it - they just figured out how to interoperate when the iPhone user turns on the far less secure "everybody" mode temporarily.
So they "cracked it"? Airdrop is Apple's proprietary protocol, google reversed engineered it to make it work, meaning they "cracked" it.
Cracking would imply Google could send me malicious files impersonating someone in my contacts, and without me switching to "everybody" mode first.
No. Cracking doesn't require bypassing every security feature.
Nobody is claiming Google can impersonate your contacts or bypass Apple's trust model. The point is that Google successfully reverse engineered a proprietary Apple protocol and achieved interoperability without Apple's cooperation.
The reason it only works in "Everyone for 10 minutes" mode is because Apple doesn't expose the information needed for the Contacts Only trust model.
And Google can't really do more for the same reason Apple wasn't able to support encryption on RCS until recently
False. Apple was always capable of supporting encrypted RCS.
Google implemented E2EE years ago using the open Signal Protocol because the Universal Profile allows vendor specific extensions. Apple chose to wait for the GSMA to standardize a multi-vendor solution based on MLS.
That was a standards decision, not a technical limitation.
- each vendor (Apple in the first case, Google in the second) is relying on a self-hosted proprietary security system based on all participants being customers.
Signal Protocol isn't proprietary.
It's an open protocol with publicly available specifications that has been independently audited and adopted by many organizations.
Apple had to work with the GSMA to create a workable multi-vendor solution and then wait for other parties to properly support it to get proper RCS support.
False.
Google spent years proposing E2EE for RCS and the carriers repeatedly rejected it, which is why Google shipped Signal Protocol encryption as an extension.
At the same time,
Google was actively participating in the IETF's MLS effort alongside organizations such as Mozilla, Meta, Cisco, MIT, Oxford, INRIA, and Wire to develop MLS which is what the GSMA adopted. Google is the one that wrote the implementation for MLS on RCS not Apple.
Google appears to be avoiding standardization and just reverse engineering a subset of Apple's current AirDrop system.
What are you even talking about?
AirDrop is Apple's proprietary file-sharing system. Apple has never standardized it or published it as an open specification.
Meanwhile, Quick Share already uses open technologies like Wi-Fi Aware (NAN). Apple could adopt those same standards for OS-level file sharing but chooses not to. If you read the history of the protocol you would know NAN and AWDS are cousins.
If anyone is avoiding standardization here, it's Apple. Google is reverse engineering AirDrop because Apple keeps it locked inside its ecosystem.