iPhone DevTeam And GeoHot Discussing Exploits For New Baseband

A few weeks ago , we told you that a possible exploit for baseband 5.12.01 was found and unlock might be on its way. And according to aModMyi thread, we are almost there. In the very near future, baseband 05.12.01 could be unlockable for those of us unfortunate enough to be stuck in this position.



Now it doesn’t necessarily mean 3.1.3 will be worked on, but its good news none the less for those unfortunate users, and for the possibility of a group effort for the next unlock between GeoHot and the DevTeam. Discussed in an IRC channel, GeoHot and the DevTeam’s MuscleNerd, share some thoughts on the exploits they have found, and by the looks of things, might actually team up to dish out an ultimate serving of Jailbreaking goodness.


GeoHot explains that there is an exploit that he had previously discovered and wanted to use with the release of blacksn0w, which has now found to still exist in 3.1.3. He goes on to discuss how he had originally wanted to implement this exploit in blacksn0w but opted to go with an open source route, which makes sense to keep things slightly on the downlow.


It sounds as though GeoHot and MuscleNerd (Dev Team) may possibly be working on the same exploit, and if that’s the case, it would be incredibly logical for them to team up rather than releasing two different exploits, which in the end could just cause more greif when upgrading in the future.

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
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

Again, we don’t expect much for 3.1.3 (Rumor has it OS 4.0 will drop mid March), but this is good news for those of you in an utterly awful situation if your phone has become more like an really expensive iPod Touch.