This is kind of reckless thinking that will put an end to jailbreaking quicker than anything else.
How would it put an end to jailbreaking any faster than not being able to release jailbreak's at all because the only way to do so includes apple code.
For me, if I couldn't have a jailbroken iPhone, I would honestly consider getting another phone
I kind of agree with dhlizard here.
Apple would be faster with updates to counter this, and would be much more hostile.
Anonymous would probably release it with preinstalled installi0us to which would be damaging to the community.
No community support on forums like this for the jailbreak at all if they included that.
You should see non-computer-literate people when they watch Anonymous on the news. I've seen a few, and they swear like its a soccer match between freedom and the wrongfully portrayed as freedomhaters Anonymous![]()
I've been a bit misquoted here. When I said Anonymous I didn't mean the infamous group but rather the definition of the word. If the brilliant minds who jailbreak the phone could release their work without having to worry about being sued they can use whatever code they need to to jailbreak the phone.
This in turn I think would be very beneficial for the jailbreak community and developers. People will be more comfortable knowing it won't take months to for a new jailbreak after a iOS update and will spend more money in the cydia store knowing their investment won't become moot because there is no jailbreak.
Think of it this way, they already jailbroke the iPhone 5. They cannot release it because it requires a Apple dev account. I will gladly pay for a DEV account if it meant I can jailbreak my phone NOW with a stable version of code. From what I read if you know what your doing a DEV account will also allow for a jailbreak no matter your version of iOS as long as the code is updated and everything that needs to be patched, is.
Apple can't loose either way with the revenue from dev accounts sold and the cydia store will flourish.
How would it put an end to jailbreaking any faster than not being able to release jailbreak's at all because the only way to do so includes apple code.
They don't give ETA's, so that must be 3rd party speculation.
To paraphrase them, They dont know when it will be released, but when they start to release video's, its not that far off.
Nope, they'll never release that one.
I didn't say developers, I just said people... pretty reliable people.
Oh so "people" that are specifically not developers say Christmas? It sure makes sense to listen to them when the developers aren't sure them self.
My mom is trying to invent a new cake, shes not sure about what ingredients she will end up using in the end. But people, pretty reliable people too are saying that it will take 1 hour and 20 minutes to make the cake at 200 degrees Celsius.
I have iPhone 5 currently running 6.1.4, since there's no jailbreak should I update to ios 7?
Stay on 6.1.4 they are working on a seperate 6.1.3/4 JB which should be ready before the iOS7 JB.
Update #9 (Nov. 1): People are probably wondering why focus on A5+ devices is being lowered in priority. This is not because of difficulties, it is actually because it turns out a few of the vulns we were planning on using still work on iOS 7 (kind of exciting [yes and no]). We do not want to publish these vulns as they have the potential of being used in a future iOS 7.x A5+ jailbreak. With that being said, we are not removing our focus on an A5+ 6.1.3/6.1.4 jailbreak completely. We are looking for some vulns that exist in 6.1.3/6.1.4 but not iOS 7. The problem is... in terms of security iOS 7 looks likes an iOS 6.2. This wouldn't be a problem if Apple did not silently kill the lockdown socket bug. We were initially planning on using that vuln to recycle the shebang attack used in evasi0n to remount the rootfs, but when I found out it was patched, I initially said it wouldn't halt the progress of the jb. This was before we found out the other vuln we had to get root and remount the rootfs as r/w still works in iOS 7. So as I said above, we are currently working on getting the A4 untether bootstrap finished. After that, we will resume looking into the A5+ possibility. If worse comes to worse, we'll release it alongside evad3r's iOS 7 jb to prevent disclosing any more vulns.