Finally another good news for those iPhone unlockers who updated their iPhone to stock firmware 3.1.3 knowingly or unknowingly. GeoHot discovered a working exploit in baseband 05.12.01, GeoHot already posted the hash of his BB exploit for safekeeping check his Here GeoHot tweeted the hash tag of his BB crash..
Update : Geohot is not going to release his unlock this weekend. We were confused with Motorama this weekend part, actually GeoHot was talking about Motorama event where he is going to showcase his green robot [Check Here] So no unlock this weekend and possibly we may have a release after OS 3.2 this march with iPad launch or may be with after iPhone 4G/ OS 4.0 in June/July event.
As you know Sheriff Hashim founds a crash for latest baseband [check the story here] and he handed the exploit to iPhone Dev team. Musclenerd also confirmed that the crash is very promising. Musclenerd didn’t promised any ETA for the Ultrasn0w update, may be dev team is looking forward to save the exploit for OS 3.2 or may be for next gen iPhone and OS 4.0
iHackintosh fantipped us the IRC conversation between him, GeoHot and Musclenerd. The following conversation clarifies that both GeoHot and Musclenerd now have a working exploit for latest baseband. Both hackers are unsure if they have same or different crashes under their hood.
<visnet_> What 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
<Evan> 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 though
<%geohot> yea, i salted the hash
<@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
<Her> 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
Stay tuned with us for your daily dose of iPhone news, you can follow us on twitter via @ihackinjosh You can
also subscribe to our daily free e-mail news letter and keep your self updated with the latest of iPhone