News for hackers. Stuff that matters.

A comment on Bitcode (iOS, watchOS). Parent comment

Re:Bitcode (iOS, watchOS) by 0x0 on Tuesday June 09, 2015 @04:29AM (#9684628)
They could already do that. They sign and encrypt the (plaintext) code segment you submit so they could easily insert a JMP to their own payload at the head of your code any time
[ Parent | on HN ]
Re:Bitcode (iOS, watchOS) by chc on Tuesday June 09, 2015 @04:55AM (#9684691)
They could also just have the kernel do whatever it wants to your program, because they control that too. If you are worried that Apple might tamper with your binaries if given the chance, using an iOS device is pure folly, because they outright control much more important parts of your system (the kernel, the UI libraries, the RNG…).
[ Parent | on HN ]
Re:Bitcode (iOS, watchOS) by vbezhenar on Tuesday June 09, 2015 @05:46AM (#9684862)
Why do they encrypt code segment? Signature is essential, of course, but encrypting looks unnecessary.
[ Parent | on HN ]
Re:Bitcode (iOS, watchOS) by 0x0 on Tuesday June 09, 2015 @05:52AM (#9684884)
It's their fairplay DRM implementation that is supposed to prevent piracy.
[ Parent | on HN ]