View Single Post
Old 12-16-2015, 05:15 PM   #12
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by HarryT View Post
The reason would be self-evident if you stopped to think about it for a while.

Amazon would almost certainly not wish it to be released until they roll out a new firmware version that patches the security flaw that BD identified. It takes many, many weeks to complete a firmware rollout (OTA firmware updates are spread out across a long time period), and nobody - not one person - has reported any sight of a post 5.6.5 firmware version. Therefore we can reasonably conclude that the JB is extremely unlikely to be released any time soon, and almost certainly not before Christmas.
I wasn't in on any of the testing, but I was a party to some of the conversations, and ....

I know BD looked into just what was involved in fixing the flaw he had leveraged with his jail break code.

And the last I had heard on that was: "Very difficult to fix, had better leave it to Amazon with the resources needed".

That is, whatever it is, it isn't a simple typo or build system configuration error that could be fixed 'over night'.
knc1 is offline   Reply With Quote