It appears that there’s a battle brewing between the developers of the jailbreak community, and this time it’s news worthy as it may affect thousands of jailbreak users.

A Dutch developer has threatened to release the source code of the SHAtter exploit, depriving the jailbreak community of a valuable tool. After the developer of TwitPanic, @iHaz3, had his site brought down apparently by a DDOS attack, he threatened to release the SHAtter source as some kind of revenge, but has since held off on carrying out the threat for now.

If you don’t already know, a well known hacker pod2g developed SHAtter exploit along with the Chronic Dev Team member p0sixninja to jailbreak iOS 4.1 on new-generation device. But when GeoHot dramatically came with Limera1n to jailbreak all devices on iOS 4.1 then he stopped publishing SHAtter exploit and saved it for later version of iPhone and iPad that is for iPhone 5 and iPad 2.

iPhone developer behind Sn0wbreeze, iH8sn0w and some other tools had the code an apparently gave it to iHaz3 who’s not related to any dev teams. Now it is hearing here and there that this guy has started publishing SHAtter’s exploit publicly which would burn this exploit.

We don’t know why iHaz3 thinks iH8Sn0w had something to do with this but hopefully this whole ordeal will be resolved before anybody releases the code for SHAtter into the wild.

Sources at MMI report:

The story can be traced following @iHaz3?s Twitter feed.TwitPanic.com was crashed by what the developer believed was a DDOS attack set up by @ih8sn0w after he and @iHaz3 had “issues.” @iHaz3 then tweeted “TwitPanic.com is attacked by a organized DOSS hit……next week SHATTer will be posted on twitter.” The jailbreak community reacted with confusion, since SHAtter – an exploit allowing unsigned execution of code in the S5L8930 bottom that could only be defeated by a new hardware design – was developed by pod2g and p0sixninja of the Chronic Dev team, not iH8sn0w. It could be that @iHaz3 was confused because the iH8sn0w hacker he believed responsible for the DDOS had previously provided the SHAtter source to him.

As the day rolled on, @chronic engaged @iHaz3 in conversation and attempted to explain that @iH8sn0w had nothing to do with SHAtter, and so releasing it would do nothing to hurt him while at the same time burning a valuable exploit which has been held in reserve since @geohot came out with limera1n. Eventually, @iHaz3 agreed to a cooling-off period, which would expire sometime today, but he has since heard from his hosting company that they have the identity of the attacker and are pursuing legal action. So, hopefully, all this will blow over.

NOTE: Few sources have claimed that iHaz3 has started distributing SHAtter’s exploit that will burn the exploit.

Stay tuned for more news and info on this topic by following us on Twitter and/or by subscribing to our RSS Feed.

[Source: Twitter; MMI]

Authors: _GadgetNews

to know more click here