Quote:
Originally Posted by Kolenka
DRM is another issue, as insecurities in the device give other avenues of attack on the DRM scheme. Many companies have service agreements with content owners saying how quickly the manufacturer will fix security flaws in their devices and/or DRM. Usually if they don't, there is some sort of penalty (Apple's agreement with music providers seemed to indicate they could pull their entire catalogs from iTunes if Apple didn't fix certain types of holes in X days). So there's contractual obligations to secure their devices in many cases.
|
Jailbreaking doesn't affect DRM at all though, so I don't think that this can really be considered a reason. It's possible to download a Kindle book without any involvement with an actual Kindle device and then strip the DRM on your computer. A jailbroken Kindle doesn't facilitate DRM removal in any way.
Quote:
Originally Posted by Kolenka
It's simpler than that: updates are messy. Say I release a patch that only changes what needs to be changed to go from 1.0 to 1.1. But wait, my users made their own modifications to 1.0 so that it isn't really 1.0 anymore. What happens when my patch collides with those other modifications? Who knows. And it could be bad.
The very real reason why this could be bad is actually the very old 1.1 update Apple pushed out for the iPhone. The SIM unlock of the time collided badly with the delta patch of 1.1 and resulted in phones that no longer worked correctly (the baseband was essentially turned into gibberish by having both the unlock and the 1.1 patch applied).
So these days, many devices don't do delta updates anymore, or they do limited deltas. There just is no real way to test out all the possible hacks and how they can interfere with an update, so developers have gotten into the habit of making sure hacks/etc can't interfere with the update. The usual result is that it disables all the hacks as part of the upgrade, as a side-effect.
|
Amazon had already been pushing updates that preserved jailbreaks and homebrew across all devices without problems for a long time now, so something is fundamentally different about this update. The developers in this forum have said that Amazon is purposely trying to prevent jailbreaking. To quote
ixtab:
Quote:
|
So, you may have realized that with their 5.3.0 Firmware, Amazon has officially declared war on the developer scene, by plugging all currently known holes which allow to install the jailbreak, and by also wiping the jailbreak and all other user-installed modifications.
|