4 ms·
As the developer of Cydia, I work very closely with the people who work on these exploits (and am often, though not quite always, seen as sufficiently "neutral"
by saurik 9y ago
As the developer of Cydia, I work very closely with the people who work on these exploits (and am often, though not quite always, seen as sufficiently "neutral" to be talking to multiple groups at once), and the primary factor for iOS 10 really is that the device is now extremely secure combined with "some of the people who previously had worked attacking the device played mercenary and 'switched sides' when Apple came by looking to hire them" (which both makes it more secure and reduces the brain power available to the side of the resistance). Apple also changed their policies for fixing bugs, even low-priority ones, to get patches out sooner (and the jailbreaks also started being forced to use higher priority bugs, so the windows of applicability for various tools has been extremely low in the last couple years).
A big thing to understand is that the jailbreaks have also become "more complex to use and maintain for the user" in addition to "less likely to be found" for the developers: the jailbreaks available for iOS 9.3 and later versions are brutal... they take the form of an app that you had to install using a tool I wrote called Cydia Impactor, which pretends to be Xcode and do all of the signing for a "free developer account". Every time you reboot your device, it is no longer jailbroken, and you have to run this app, which sometimes doesn't work (on iOS 10 I'd even say it "only" sometimes works ;P); and the app itself expires every 7 days (Apple restriction on free developer accounts), and so you have to keep reinstalling it using Impactor. Finally, if you break anything at all that causes SpringBoard to not be able to pop up (as you need to get all the way to "I can see this app and click it" for the jailbreak to work), you have to format your device (losing all your data) and restore to fix it... older jailbreaks were much more forgiving, as you could still log in via SSH if the device even sort of was able to start.
I'll also say that the general issue you bring up was also true for iOS 7 and 8, but there were tons of people who jailbroke even with iOS 9. When jailbreaks are available and easy to use, developers do cool things that are able to tempt users to do it; it is like: why does anyone install an app when I bet they don't really need it? Well, spending $3 for some random app that only slightly affects what you do is worth it: the cost is low to match the low benefit; so it doesn't really matter that much if the benefit isn't "insane killer thing that everyone has to do or the phone is worthless": it only has to be greater than the cost, and the cost went up so high and so fast during the past year and a half that even I have been "living without" a feature I used every single day numerous times and am constantly sad to not have right now, because "damn it, I just don't want to have to spend ten minutes rebooting my phone over and over again in the hope that this broken jailbreak works".
- canuckintime 9y agoAnother factor is that previously the last point update of an iOS version was always jailbreakable. So there was the long period over the summer where there was a stable jailbreak that people could experiment with and utilize while Apple was focused on the next big iOS version. Now Apple is very aggressive about making sure the most recent iOS version is locked up and preventing downgrades.
- 616c 9y agoNeedless to say those who follow contemporary history of the jailbreak scene, let alone the whole history, you are a founding father. Thanks for everything you do. In the last year or so I wanted to take an old iPhone 5s, a handmedown from a relative, to learn CyScript and the other one from the NowSecure engineer that exposes a JS interface (I forget). How can and how will security students learn to reverse engineer at runtime and assess modern iOS apps in the current state and no official emulator to boot?