It's been a pretty exciting weekend in the jailbreak community as @planetbeing and @pod2g tweeted tidbits of progress on the iOS 6, 6.0.1, 6.02 or 6.1 untethered jailbreak for iPhone 5, 4S and other non-jailbroken devices. It seems our favorite developers took full advantage of the long weekend working steadily, and as a result, the entire community is feeling that the jailbreak scene has been revived. Earlier today, @pod2g tweeted something that looked to be another positive step.
"Hey @planetbeing, please look at your IRC, I think I have good news!"
So what's been happening? Well, here it is in a nutshell.
About 2 ½ weeks ago @planebeing posted to Reddit the news we'd been waiting to hear for quite some time: He had an iOS 6.0.2 untethered jailbreak for iPhone 5 working but unfortunately not yet prepared for public release.
Here is what the post said:
"Yeah, I'm not really sure what all the doom and gloom is about. The fact is, I have an untethered iOS 6.0.2 JB running on my iPhone 5 right now."
Since that time, both he and @pod2g have become increasingly more present on Twitter, engaging with fans, answering questions, and revealing small tidbits of progress. Just yesterday we were excited to see more news that the iOS 6, 6.0.1, 6.0.2 or 6.1 untethered jailbreak was even closer to completion as @planetbeing and @pod2g filled us in on where they were:
"Made some nice progress today with @pod2g. I think I'll try to reward myself with a nap." Tweeted @planetbeing.
To which @pod2g added this:
"Oh yeah! 2 new vulnerabilities in a day, chance was with us. But we still miss that initial code execution for a public jb."
Later that day, @planetbeing was good enough to fill us in further on what work still remained:
"Pod2g discovered a vulnerability and told me about it and I tried to integrate it into my existing jailbreak code to replace one of the ones we don't want to burn. I discovered I couldn't get his to work due to some miscommunication, but in the process of trying to get his to work, I discovered a new vulnerability for doing the same thing. I did get THAT one to work and it's now integrated with the rest. Unfortunately, as pod2g says, neither bug has to do with initial code injection, which we currently don't have duplicate/backup vulnerability for at all."
As exciting as this news was, even more moving to me was the fact that it seems a number of developers, both well-known or not so well-known, appear to be taking a part in the current challenge of jailbreaking iOS 6, 6.0.1, 6.0.2, or 6.1 untethered for iPhone 5, 4S and other non-jailbroken devices.
Here's just a sample of players I've seen who are stepping up, helping out and supporting the entire jailbreak process:
When @aaronash, author of Barrel and Multifl0w, saw the guys were still searching for pieces, he quickly chimed in with this:
"I have some ideas for initial code exec, I couldn't test everything, but you might be able to (check IRC). "
Though Aaron recently informed me the idea he had didn't end up working, it's still encouraging to see his desire to contribute.
Meanwhile, others developers around saw the hang-up @pod2g and @planetbeing were facing, and an interesting discussion emerged.
First developer, jduck1337 started by questioning why this initial code was such a big deal, saying that "That should be the easy part..."
Seeing this comment IT security guy, @SwissHttp, and administrator on geohot's theiphonewiki.com offered this tidbit for clarification:
"Easy part: On iOS there's not a big attack surface, it's not like a desktop machine, on ATV even less. You have something?"
To which, @jduck1337 had this reply:
"Whats the prob with the piles of already disclosed but not patched webkit bugs?"
At this point @p0sixninja's Twitter lit up:
"Sandbox isn't a huge issue, we just haven't dug into webkit to much (except @comex)"
Hearing this @SwissHttp tweeted,
"Good to know. Maybe I'll have a look then, if I find some time."
In addition on Monday we saw @pimskeks tweeting out that he was also still in the game:
"Dear followers I'm not dead. I'm still doing security research and jailbreaking. I just needed time for my family! "
And indeed, with the welcome of a new little one to the Bassen household last fall, no one certainly can blame him for putting the wee one first.
So right there folks were are looking at four former iPhone Dream Team members and 2 additional jailbreak community members helping the cause--not to mention the ever-so-modest and behind the scenes worker, Saurik, we heard had been helping @pod2g not too long ago.
When @Pod2g first announced his return to the jailbreak, some were doubtful, fearing his app business would be the end of his jailbreak days. But Saurik put those fears to rest stating this on Reddit:
"I actually was working with pod2g (albeit with a worse headache than I've had in at least a year, so mostly as a "gdb test monkey"), and can thereby personally attest that he didn't just say it, he actually did it."
Of course being the modest fellow he is, he made sure to follow up and let people know who was really the center of the project:
"Planetbeing ... actually has the stuff that works, and I'm mostly just around to occasionally make people less lonely as they work on things ... I found a few issues myself, but I don't know if they could be turned into a jailbreak..."
Well jailbreak ready or not, we certainly appreciate a founding father of the jailbreak scene, and developer of Cydia store keeping the lead players "company" as they work on the iOS 6, 6.0.1. 6.0.2 or 6.1 untethered jailbreak for iPhone 5, 4S and other non-jailbroken devices.
What's really exciting to me this time around, however, it the way it seems the jailbreak scene has grown and changed. Developers are now working together, not against one another and no one seems to care if they are getting the credit right or not. To me it seems a true "Dream Team" is being born.
As @planetbeing posted on his Twitter account recently, with Apple security at the place where it is now, it indeed takes a full army of minds and hands to achieve the feat of a jailbreak. When one user asked if he thought there could ever be any "moles" in the jailbreak community who could leak information to Apple, here is what @planetbeing posted:
"The only way you'd be able to place an agent is to actually have them contribute very significantly to the development of a jailbreak in the first place ... Even if you contribute just a bug or two, there's still a lot of compartmentalization of knowledge and need-to-know ... I don't think we even really have "teams" anymore for better or for worse anyway, an individual just knows what the discoverer of something thinks they should know ... The "dream team" for example is not any sort of organization, just the people who helped on that particular jailbreak..."
So what we have then is a conglomerate of like-minded people contributing in any way they possibly can to the cause, none worried about glory but all moving toward a common goal. Sure there are some who may hold more pieces to the puzzle than others, but without every part, the entire thing would never come together. My hope is, as the story unfolds, I can shed some light on the lesser-known contributors while also singing the praises of the forerunners in the iOS 6, 6.0.1, 6.0.2 or 6.1 untethered jailbreak for iPhone 5 and other non-jailbroken devices.
Just keep in mind, that though we are a step closer, it's very possible we could have a decent wait ahead--if you haven't seen it, check out @planebeing's reasons why he ever gives an ETA.
Stay tuned friends, as no matter what happens, I will be keeping you updated on the progress from my small corner of the universe.
or like her Facebook Page for her latest stories and updates.