Looks like a bunch of people will be stuck on 6.1 because I have a feeling these holes should be patched up for the next build. Why people decided to post almost every detail of the jailbreak instead of letting Apple guess is beyond me.

Looks like a bunch of people will be stuck on 6.1 because I have a feeling these holes should be patched up for the next build. Why people decided to post almost every detail of the jailbreak instead of letting Apple guess is beyond me.

I liked this 'how they did it' explanation:
»blog.accuvantlabs.com/blog/bthom···omponent

Nice, but why post the freakin recipe? Just makes it easier for Apple to close the loopholes...

I'm convinced at this point Apple makes these things just hard enough to jailbreak to seem like it's an accomplishment, but not so hard as to be impossible.

This Unix internals person cringed at
"it uses a Unix trick called a “shebang” that can summon up code from another, signed application. "

»en.wikipedia.org/wiki/Shebang_%28Unix%29

This isn't a "Unix trick". This is how shell files indicate what shell they need to interpret themselves. If THAT is the security hole in iOS, it's time to fire the security review team. Wow.

"Wang won’t say exactly how that AMFID-defeating part of the jailbreak works. “Apple can figure that one out for themselves,” he says." and then he goes on to explain how they defeated ASLR (which has been defeated many times) so, clearly, they're patching stuff in memory to defeat AMFID - not unlike the Surface RT hack that lets you run unsigned code on RT.

Nice hack. I'm convinced at this point Apple makes these things just hard enough to jailbreak to seem like it's an accomplishment, but not so hard as to be impossible. The exploits used here are actually fairly critical security holes in iOS, they have to have been left purposefully. If not, then as I said some people should be looking for new work.