I'm sure someone will download the APK and decompile it. Hopefully the source hasn't been obfuscated.

It looks a bit obfuscated, but there might be some useful finds. I'm going through it and looking for hardcoded strings that might not be in the resource files.

I posted the APKTool output on Github for anyone that wants a quick look - https://github.com/mdp/iMessageChatDecompile

if someone can reverse-engineered the protocol,then it is not very much difficult to reverse-engineered the obfuscated apk.

It has: https://twitter.com/stroughtonsmith/status/38236591736120934...

Kudos to the folk who reverse-engineered it, but I'm not sure this is a good thing in the long run.

Put it this way, just like AirPlay and AirDrop, it keeps the open-source community on the backfoot, always looking to "keep up with the Joneses" when in fact we should let these proprietary protocols wither and die.

The public perception shouldn't be that Apple lead and others follow, it should be that Apple have deliberately isolated themselves from everybody else.

I agree with you. I also suspect Apple's iMessage system is not nearly as secure as they claim it is. So if someone can post the full crypto protocol, others will find bugs/ backdoors* in it and you will have one more reason not to trust closed source secure communication software.

* By backdoor, I mean the protocol isn't actually end to end secure in the way Apple claims(i.e. safe from NSLs) and Apple does actually have access to messages. Not that the protocol looks secure and they picked backdoored primitives or some secrete key escrow scheme, though they may have done the latee at least in other cases[0]

[0]http://www.nosuchcon.org/talks/D1_02_Alex_Ninjas_and_Harry_P...