3 ms·
It should be pretty easy to work around this, either by hacking around (e.g. with a debugger) whatever call was used to disable UI scripting, or by using the in
by comex 10y ago
It should be pretty easy to work around this, either by hacking around (e.g. with a debugger) whatever call was used to disable UI scripting, or by using the interface between Messages.app and the IMCore framework, which is a relatively high-level Objective-C API. On the other hand, for the record, reimplementing an iMessage client from scratch would be difficult due to DRM: while the protocol is generally sane, it includes an authentication layer based on FairPlay, involving heavily obfuscated code. Some information here, though I'm not sure if it's up to date:
http://imfreedom.org/wiki/IMessage http://imfreedom.org/wiki/IMessage
- brianwawok 10y agoIf you aren't jailbroke, can't they just set it up so no one but program X can access API Y, at the OS level? Apples house, Apples rules.
- comex 10y agoThe linked project is for OS X, not iOS.
- brianwawok 10y agoOpps
- PhantomGremlin 10y agoby hacking around (e.g. with a debugger) In 10.11 Apple added System Integrity Protection[1][2], so it might not be as simple as it once was to hack preinstalled apps. From wiki: Most preinstalled Apple applications in /Applications are protected as well. The kernel stops all processes without specific privileges from writing to flagged files and folders. It also prevents code injection, runtime attachment (like debugging) and DTrace [1] https://support.apple.com/en-us/HT204899 https://support.apple.com/en-us/HT204899 [2] https://en.wikipedia.org/wiki/System_Integrity_Protection https://en.wikipedia.org/wiki/System_Integrity_Protection
- umanwizard 10y agoSIP can be turned off easily.
- comex 10y agoSIP can be disabled by the user by design, but yes, it would require doing so.