In a better world not owned and locked down by a few jerks like we have now, I'd have a multiboot in my pocket phone running whatever flavor of OS I felt like on a particular Tuesday.
You don’t just rewrite a complete operating system. Maybe it is some sort of please hire me call from young professionals who didn’t think it through entirely.I suspect Corellium didn't copy one line of code and wrote it themselves from scratch. The only thing copied were icons and graphics.
But what if you want to virtualize iOS in Windows?
Look up clean room reverse engineering. They don't need apples permission to do that.
Did Apple 'Steal' the code from Google or did Apple write it's own implimentation of the Google App? There is a huge difference between the two.Poor Apple. You dummies gonna pay up cash to Google for stealing Notification Center from them? Annnnd 99% of all the other things you’ve stolen from Android, you dirty thieves? Year after year after year.
In a better world not owned and locked down by a few jerks like we have now, I'd have a multiboot in my pocket phone running whatever flavor of OS I felt like on a particular Tuesday.
In order to provide a platform to hunt for security holes, they would need to run iOS itself, not some approximation that looks and feels like iOS. So my guess is that Correlium provides a software layer between the hardware and the OS that fools iOS into thinking it's being installed on an Apple device. Further, this must allow installation of not just Apple's OS, but also the firmware underlying it, since firmware bugs are an important part of security testing.
So when someone is using Correlium to test iOS, my thinking is that they're not running a reverse-engineered version of iOS created by Correlium. Rather, they are running an official Apple version of iOS (software+firmware), which Correlium allows them to install on a non-Apple device.
In a better world not owned and locked down by a few jerks like we have now, I'd have a multiboot in my pocket phone running whatever flavor of OS I felt like on a particular Tuesday.
I feel like the article and lawsuit are very misleading. Clearly Corellium haven't copied anything from Apple, except probably the picture of the phone frame around the screen. It's an emulator. It runs the iOS software. They didn't copy it.
As someone already said, Xcode provides a simulator, which is not the same as an emulator. The simulator runs code on x86 (so, completely different instruction set), has all the Mac RAM free to use (more than an iPhone), lacks some things like Bluetooth connectivity, etc.
The allegation that Corellium didn't require purchasers to provide info to Apple is laughable. Security researchers that need this tool don't work for Apple obviously. This doesn't mean they're looking for bugs to resell on the black market. There are companies that sell services where they provide increased security to companies by discovering vulnerabilities and creating workarounds/mitigations (firewall rules, antivirus checking for potential exploits, etc).
MacRumors should get in touch with Corellium and revise the article.
Apple's claims of infringement sound legitimate, but this phrase seems over the top to me:
Corellium makes no effort whatsoever to confine use of its product to good-faith research and testing of iOS.
Suppose for a minute that they hadn't violated Apple's IP and were instead offering this service with a license from Apple. If a product or service like this can be used for both proper and improper or illegal purposes, must the company make efforts to "confine the use" to proper purposes, and be legally liable or subject to lawsuits if they do not?
Sounds like Apple should just buy them and use the virtual iOS as a tool for developers and researchers looking for exploits, better than handing out locked down devices to everyone.
Obviously you are not familiar with the early days of PC development where BIOS code was developed to recreate IBMs / MicroSofts copyrighted code. The question will come down did they recreate or steal. As it si the article is so poorly written that I'm not sure what exactly they are doing here. Apple will have a hard time fighting virtualization, if all Corellium does is to load IOS into an emulated IoS devices "hardware" I really don't wee Apple having a case. If they did all sorts of companies involved in virtualization will be at risk.Apple has a good case against them, I suspect Corellium won't have much of a chance defending themselves. You can't recreate someone's intellectual property without asking, especially code that is owned by Apple.
Obviously you are not familiar with the early days of PC development where BIOS code was developed to recreate IBMs / MicroSofts copyrighted code. The question will come down did they recreate or steal. As it si the article is so poorly written that I'm not sure what exactly they are doing here. Apple will have a hard time fighting virtualization, if all Corellium does is to load IOS into an emulated IoS devices "hardware" I really don't wee Apple having a case. If they did all sorts of companies involved in virtualization will be at risk.
The real answer here is that Corellium doesn't have the deep pockets to sustain years long legal action.
Finally a sensible comment in this thread. They've not decompiled and recompiled, or stolen source code or written iOS from scratch, they've just virtualized the environment on which the actual code, iOS, plus all the apps, run. They've emulated all the hardware the device provides so iOS and app code runs just as it normally does. No mean feat, and to accomplish it they certainly took a very deep dive into the operating system.
This is quite different from the iOS simulator on Xcode which has a complete x86 version of iOS compiled for the simulator from the actual iOS source (which of course only Apple could do) and requires apps compiled for x86 and linked against the simulator libraries.