General Disclaimer: To start with, the US government has deemed it completely acceptable to jailbreak your iPhone, iPod touch, Apple TV, or anything else you want for that matter. If you purchased the device, it’s yours to do what you want with it.
That being said, if you void your warranty, you’re on your own. Apple doesn’t have to fix it, Apple doesn’t have to replace it, and you shouldn’t think for one second that they should.
Now that we got all that ‘where we stand’ junk out of the way, we can say with certainty that something smells rotten in the state of iBooks. Jailbreakers rocking GreenPois0n noticed that they’re having a hard time getting access to DRM based iBooks. On the surface it seems like the blocks and hurdles have to do with iBooks and the iBookstore. I say seems, because we have no proof that Apple set out to thwart jailbreakers with this move. Actually, we have some proof that this has more to do with the Fairplay DRM checks put into place than it does with anything Apple did.
Apple hasn’t updated iOS recently, so this code has been around for a while at the very least. According to PushFix, the current DRM system that’s failing has been around since iOS 4.0, which, in case you haven’t guessed, has been around longer than GreenPois0n. We live in a DRM world, and like it or not, publishers want to protect their copyrights. Say what you will about Apple and their intimate relationship with DRM, but don’t pretend for a moment that they’re responsible for the DRM problems today.
Let’s get this straight: It’s not Apple
It’s pretty crappy that people who jailbreak can’t use DRM based iBooks, but in this chicken and egg scenario, what came first? An iOS update that brought with it a FairPlayd check or the GreenPois0n jailbreak? Like I said off the top, if Apple put this into place as a stop-gap solution to jailbreaking, then it’s a pretty lame move. But I have a feeling that this DRM problem has more to do with GreenPois0n than it does with Apple. Actually, there’s a pretty good indication that this has everything to do with FairPlay’s check and GreenPois0n, and nothing to do with Apple at all.
But that’s just my opinion, what’s yours? Sound off in the comments.
Push Fix on Twitter is dispelling a lot of the FUD about this problem. They’ve pointed out that the protection code that’s the root cause of the problem has been around since iOS 4.0. If you want to stay up-to-date with this breaking news, then you’re going to want to follow them. We’ll try to provide updates here when we can.