Live data from Hacker News

iPhone 11 emulation done in QEMU

github.com

11–20 of 35 posts

Re: iPhone 11 emulation done in QEMU

#11
post #6

Earlier quoted context omitted.

Looking at the issue tracker it sounds like they've made significant progress since then.

Progress update, https://eshard.com/posts/emulating-ios-14-with-qemu-part2 iOS emulated in QEMU with: • Restore / Boot • Software rendering • Kernel and userspace debugging • Pairing with the host • Serial / SSH access • Multitouch • Network • Install and run any arbitrary IPA In other news, Cellebrite acquired Corellium iOS/Android virtualization for $170M, https://news.ycombinator.com/item?id=44221982

Presumably to build a exploit test framework.

Re: iPhone 11 emulation done in QEMU

#14
post #3

Does it support trollstore with ability to decrypt IPAs?

For the ignorant: what does this mean?

Just to expand a bit on the sibling comment, IPAs downloaded from the App Store are encrypted with a DRM scheme with a key tied to the Apple account. The binaries actually stay encrypted on-disk and the OS has facilities to transparently decrypt them when executed. The usual way of decrypting is to actually execute the app, attach a debugger (normally not possible for production apps) and read the decrypted code from memory.

Re: iPhone 11 emulation done in QEMU

#15
post #6

Earlier quoted context omitted.

Looking at the issue tracker it sounds like they've made significant progress since then.

Progress update, https://eshard.com/posts/emulating-ios-14-with-qemu-part2 iOS emulated in QEMU with: • Restore / Boot • Software rendering • Kernel and userspace debugging • Pairing with the host • Serial / SSH access • Multitouch • Network • Install and run any arbitrary IPA In other news, Cellebrite acquired Corellium iOS/Android virtualization for $170M, https://news.ycombinator.com/item?id=44221982

The eShard thing and this GitHub are fairly different, as far as I know.

The eShard people found an earlier version of this repository and set about patching one billion parts of the iOS kernel, library cache, and userland to make it run on the limited emulator.

Meanwhile, the actual emulator has been advancing, arguably more quickly than the eShard patch set.

The current set of patches needed for the latest commits on this repo to run iOS are less than 10 instructions, all to enable the software-rendering/framebuffer fallback code path instead of trying to use display drivers.

https://github.com/ChefKissInc/QEMUAppleSilicon/wiki/Filesys...

Re: iPhone 11 emulation done in QEMU

#18
This is the ultimate emulation hack bar none - congrats to everyone involved. This also bodes well for the hackintosh project. It's may no longer be a dead end (though miles away), and eventually we might even see efficient emulation as ARM PCs become generally available.

Re: iPhone 11 emulation done in QEMU

#19
post #18

This is the ultimate emulation hack bar none - congrats to everyone involved. This also bodes well for the hackintosh project. It's may no longer be a dead end (though miles away), and eventually we might even see efficient emulation as ARM PCs become generally available.

ARM is not an open platform like IBM PC was. See Android phones and their custom Linux kernels with undocumented parts...

Re: iPhone 11 emulation done in QEMU

#20
Seems like the important part would be emulating the security crap so it can be understood and bypassed. Where is this with that set of things? (being able to run things like banking/DMV emulated would be the killer feature)
Post reply on HN