Dev Team And Chronic Dev Team Comment On Geohot’s Limera1n; Greenpois0n Delayed

News | Sunday October 10 2010 3:45 AM | Comments (0) Tags: , , , , , ,

After a few very dramatic days in the jailbreak community, geohot has come out of nowhere to release limera1n. It’s a bootrom-level jailbreak that works on the iPhone 3GS, iPhone 4, iPod touch 3G, iPod touch 4G, the iPad, and (technically) the AppleTV 2G.
[…] Limera1n uses a different exploit than SHAtter, and in fact covers more devices. Although some may question geohot’s dramatic and competitive style, he obviously does have considerable skill pulling this together in just over a day (although he’s had the underlying exploit for months). Credit also goes to @comex, who provides the untethered aspect of limera1n via another one of his growing list of kernel hacks.
The release of limera1n has (hopefully!) averted the burning of 2 bootrom holes at once (both his and SHAtter). Releasing SHAtter now would be a complete waste of a perfectly good bootrom hole in light of limera1n, and so it can be held until Apple closes limera1n’s hole. While there’s no guarantee that Apple won’t also close SHAtter by then, it provides a ray of hope for devices after Apple ’s bootrom respin. Meanwhile, look for an alternate implementation of the limera1n exploit in greenpois0n (and possibly other tools), where it should undergo more testing too.
Meanwhile, Chronic Dev were left with three options after Geohot released limera1n according to
we have 3 options, A) Not release greenpois0n, B) Burn a second bootrom expoit, or C) Break our ETA and implement geo's exploit
Chronic Dev team have decided to go with option C. They have just published a post to inform users that greenpois0n would be delayed as they plan to incorporate the exploit used by Geohot in limera1n:
Thanks to the irresponsible antics of geohot, we will have to delay the release of greenpois0n (new ETA = as soon as possible), so that we have time to clean up his little mess and integrate the exploit he uses in limera1n into greenpois0n. This way, we can save SHAtter for future devices that may still be vulnerable to it.
We know that this is not what some people want to hear, but due to geohot needing to feed his ego (as usual) and revealing his limera1n exploit, we do not have any other responsible options.
Geohot has defended his decision of releasing limera1n, a day before greenpois0n was released, by saying that it was to
, which as Dev team has mentioned was to avoid burning 2 bootrom exploits at once as Geohot felt SHAtter was a more superior and could be used for future devices. So all the hard work that Chronic Dev team had put in developing greenpois0n over the last few weeks should come in handy in the future.
It's a pity that the Dev Team, Chronic Dev Team and Geohot can’t work together as one happy family. It probably would have made it even more difficult for Apple to stay ahead of the cat and mouse game.
What’s your take? Tell us in the comments.

No Comments »

No comments yet.

RSS feed. TrackBack URI

Leave a comment

You must be logged in to post a comment.