A few days ago, we reported that Shref Hashim found an exploit to unlock iPhone Baseband 05.12.01 and handed it over to the Dev-Team. Later Musclenerd, from the Dev-Team confirmed it as a promising exploit.
Here’s some exciting news for all those who lost their unlock due to updating their iPhone firmware to OS 3.1.3. GeoHot, the first unlocker of iPhone 2G and father of jailbreak and unlock tools like BlackRa1n and BlackSn0w and the PS3, has revealed that he has an exploit to unlock iPhone Baseband 05.12.11.
In an IRC conversation with @visnet_, @Par4doX, @Evan, @MuscleNerd, @He, GeoHot has revealed that he has an exploit to unlock iPhone Baseband 05.12.01. Actually GeoHot had two exploits to unlock baseband 05.11.07. But he used xemn in BlackSn0w since it was already public. The second exploit is still there and carries over from 05.11.07 to 05.12.01.
Now the question is, do the both Dev-Team and GeoHot have the same exploit? Musclenerd, has suggested GeoHot to figure out a way to check if they both have the same exploit or different otherwise they may release 2 different ones at the same time which would not be favorable to the jailbreak and unlock community.
Let's hope GeoHot listen to Musclenerd and then develop an unlock solution accordingly. Checkout the conversation:
Follow us to Twitter, and also Subscribe to RSS Feed to receive latest updates on unlocking iPhone Baseband 05.12.01What does geohot tweet mean?
<%geohot> its my bb exploit for safekeeping
<%Par4doX> geohot: did you turn that over to the dev team or are you doing something with it?
<%geohot> my days of turning things over are done
<%geohot> i hope its different from the one they have
<%geohot> but they prob already have it
<%geohot> its the one i orig wanted to release blacksn0w with
<%Par4doX> it’s still there in the new bb
<%geohot> yep, just checked
<%geohot> but then opted to use xemn since it was public
Oo, it carries over from 05.11 to 05.12?
<%geohot> why wouldn’t it, apple doesn’t fix things proactivly
<@MuscleNerd> geohot we prob should figure out a way to know if we have same exploit double blind, otherwise we may release 2 different ones at same time
<%geohot> any suggestions?
<@MuscleNerd> not sure how to do that without making it easy to brute force tho
<%geohot> yea, i salted the hash
<@MuscleNerd> yeah
<@MuscleNerd> hmm maybe if we both hash the stack dump
<@Confucious> Can you two take this out of public sight?
<@MuscleNerd> the stack itself, not the header before it or the registers after it
muscle: any notice about the exploits are the same ?
<%geohot> we are working on it
<%geohot> cryptography, perfect for people who don’t trust each other
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.