Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

You do not need to jailbreak to pirate, and most people who pirate don't jailbreak: the way people pirate is they either download applications from China that use enterprise certificates (which Apple vaguely tries to find and stop by revoking the certificate, but doesn't do very well at) or they share developer certificates (you can even pay a tiny subscription fee to get your device added to someone else's account with a download link for a wildcard provisioning profile), and then they can just install whatever they want to their device. Even the US Copyright Office has gone explicitly on the record as stating that they do not feel there is a link between piracy and jailbreaking mobile phones (unlike for other categories of device, such as video game consoles, where they consider that problem to exist and be serious).


The China Enterprise certificate thing is simmering down actually. I have been watching the "helper" apps, and there seems to be a shift to using iTunes APIs and an AppleID/password combination to sign via Xcode, like Impactor. Additionally there is a "repair" functionality to make the 7-day thing less of a pain.

Your point still stands of course: Jailbreak is not at all needed for privacy.


Hi Saurik, my reasoning was obviously not very well researched; actually I can see its a damaging assumption for the PR of jailbreaking when I (or the public in general) makes assumptions that jailbreaking is strongly linked to game piracy, so its appreciated you were able to clarify.

I personally have held my iPad back on iOS 9 for the reason that maybe some day I could jailbreak and install another OS, home brew apps etc. but I made a generalization about piracy I guess because I did see a bunch of demand for that in 2010-2012 which shows you how out of date my iOS knowledge is (since I have not jailbroken any devices between then and now). By the way, thanks for Cydia :) its synonymous in my mind for any discussion about jailbreaking and iOS.

I just think there is some demand for jailbreaking, and lack of public demand isn't a significant explanation for lack of jailbreaking progress on iOS 10/11. I mean, there is no clear argument I've seen yet which establishes a link between public demand and frequency of jailbreaks; after all it only takes a single determined developer/hacker to craft an exploit and deploy it for reasons not connected to public demand.


> I just think there is some demand for jailbreaking, and lack of public demand isn't a significant explanation for lack of jailbreaking progress on iOS 10/11.

For the most part, I agree with this, and I was making this argument somewhere else in this thread: the primary reasons that we haven't seen many or, when they happen, "pleasant" jailbreaks for recent versions of iOS is that Apple has continued to be good about not having severe regressions in their attempts to secure the device, they have added really interesting mitigations ahead of the competition, they have changed their prioritization for plugging holes (they used to let jailbreaks sit around for months), and they've hired many of the more "mercenary" people who would work on jailbreaks away from The Resistance to work for The Empire.

That said, there is at least some connection with demand, and that's something worth examining in more detail here.

> ...after all it only takes a single determined developer/hacker to craft an exploit and deploy it for reasons not connected to public demand...

The way you word this sentence makes it sound like the work involved here is comparable--not just in quantity but in concept--to building a real-time chat application or some other slightly-complex web application. This isn't just "work": it is a combination of luck and skill that relies on winning a game that you are playing against an opponent (Apple) who had to make a mistake; if anything, it has more in common with panning for gold than building a bridge. One does not just "craft an exploit", no matter how determined.

The reason people are willing to burn tons of time into the possibility of finding a vulnerability in this platform is because there's a ton of PR and excitement to come from it, which is largely tied to the amount of interest that exists. There are tons of less secure devices out there that never get anyone bothering to "jailbreak" them due to lack of interest; people even take up bounties to try to get these devices hacked. This is made much worse as there really aren't that many people who can even pull this off when given an end-to-end explanation of a vulnerability.

What ends up happening, thereby, when there isn't much of a public interest in jailbreaking, is that these people spend their time working on hacking other devices or they hoard their exploits (as why bother burning your magic trick on people who don't even care for the performance?), whether for personal use (it makes a great parlor trick while also letting you do a lot of great research into the workings of Apple's software) or to sell for a profit (which might be to Apple through their bug bounty program or to a third party; the latter brings up interesting ethical questions, but people definitely do it: these exploits are then used either to do more research or are turned into weapons).

We can then ask "why has demand in jailbreaking decreased? as in, why does this matter?", and I see a few reasons: one is that Apple has started "throwing in the kitchen sink" (seemingly after waiting for Steve Jobs' body to be cold in the ground...), another is that the extremely killer and pressing needs have started to go away as Apple fleshes out the operating system as well as allows more things into their App Store, and another big one is a kind of "death spiral" that comes from there being less to do, leading to fewer people bothering to do it, leading to less reason for developers to develop cool stuff, which is why there's less to do... this collapsing market is a really tough sell.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: