The Quest for Unlocking 3.1.3 - GeoHot and DevTeam Discuss Exploits

محروم.كوم · #1 02-21-2010, 07:53 PM

Well folks, we're 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.

Here is the excerpt posted by @visnet's twitter that is going around from the IRC Channel.

Quote:
What does geohot tweet mean?
its my bb exploit for safekeeping
geohot: did you turn that over to the dev team or are you doing something with it?
my days of turning things over are done
i hope its different from the one they have
but they prob already have it
its the one i orig wanted to release blacksn0w with
it’s still there in the new bb
yep, just checked
but then opted to use xemn since it was public
Oo, it carries over from 05.11 to 05.12?
why wouldn’t it, apple doesn’t fix things proactivly
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

any suggestions?
not sure how to do that without making it easy to brute force tho
yea, i salted the hash
yeah
hmm maybe if we both hash the stack dump
Can you two take this out of public sight?
the stack itself, not the header before it or the registers after it
muscle: any notice about the exploits are the same ?
we are working on it
cryptography, perfect for people who don’t trust each other

منقووول __DEFINE_LIKE_SHARE__