|
The iPhone Wiki is no longer updated. Visit this article on The Apple Wiki for current information. |
Difference between revisions of "Greenpois0n (jailbreak)"
(clarify date by using a format everybody understands, added some links) |
|||
| Line 12: | Line 12: | ||
== Jailbreak == |
== Jailbreak == |
||
| − | |||
Greenpois0n was originally written using two exploits; the [[SHAtter]] [[bootrom]] [[exploit]] as well as a userland [[exploit]] provided by [[Comex]] to make the jailbreak untethered. A release date of 10/10/10 10:10:10 AM (GMT) was announced, as well as the list of supported devices. Due to the nature of the [[SHAtter]] exploit, only iDevices using the [[S5L8930|Apple A4 Processor]] were supported. |
Greenpois0n was originally written using two exploits; the [[SHAtter]] [[bootrom]] [[exploit]] as well as a userland [[exploit]] provided by [[Comex]] to make the jailbreak untethered. A release date of 10/10/10 10:10:10 AM (GMT) was announced, as well as the list of supported devices. Due to the nature of the [[SHAtter]] exploit, only iDevices using the [[S5L8930|Apple A4 Processor]] were supported. |
||
| − | [[user:geohot|geohot]] later released another jailbreak ([[limera1n]] using a different bootrom exploit) on |
+ | [[user:geohot|geohot]] later released another jailbreak ([[limera1n]] using a different [[bootrom exploit]]) on 9 October 2010, delaying the release of [[Greenpois0n]] together with the [[SHAtter]] exploit. |
| − | Currently, the Chronic Dev Team is in the process of re-writing Greenpois0n to use the limera1n exploit. ETA for release is currently unknown. |
+ | Currently, the [[Chronic Dev Team]] is in the process of re-writing [[Greenpois0n]] to use the limera1n exploit. ETA for release is currently unknown. |
=== Controversy === |
=== Controversy === |
||
| − | |||
There was much controversy surrounding the sudden release of [[limera1n]] and the motives behind it. The main reasons for the [[limera1n]] release were: |
There was much controversy surrounding the sudden release of [[limera1n]] and the motives behind it. The main reasons for the [[limera1n]] release were: |
||
Revision as of 07:09, 12 October 2010
Greenpois0n is both a cross-platform hacker toolkit (that helps users to find their own exploits for jailbreaks, write custom ramdisks, and create custom firmwares) as well as a yet unreleased jailbreak tool for iDevices written by the Chronic Dev Team.
Current Toolset
- GreenPois0n Cyanide: iBoot payload toolkit to help developers discover new vulnerabilities and design super fast, low-level iBoot jailbreaks and exploit payloads, much like the way blackra1n/purplera1n works.
- GreenPois0n Dioxin: MobileDevice toolkit designed to help developers design awesome userland jailbreaks, like how Spirit works.
- GreenPois0n Anthrax: iPhone ramdisk toolkit to help developers design extremely stable and portable ramdisk jailbreaks, much like the same way QuickPwn/redsn0w works.
- GreenPois0n Arsenic: custom firmware toolkit to help developers design jailbreaks to help preserve baseband and keep unlocks, much in the same way PwnageTool/sn0wbreeze works.
Jailbreak
Greenpois0n was originally written using two exploits; the SHAtter bootrom exploit as well as a userland exploit provided by Comex to make the jailbreak untethered. A release date of 10/10/10 10:10:10 AM (GMT) was announced, as well as the list of supported devices. Due to the nature of the SHAtter exploit, only iDevices using the Apple A4 Processor were supported. geohot later released another jailbreak (limera1n using a different bootrom exploit) on 9 October 2010, delaying the release of Greenpois0n together with the SHAtter exploit.
Currently, the Chronic Dev Team is in the process of re-writing Greenpois0n to use the limera1n exploit. ETA for release is currently unknown.
Controversy
There was much controversy surrounding the sudden release of limera1n and the motives behind it. The main reasons for the limera1n release were:
- Use an exploit that Apple already knew about (newer iBoots shows the exploit patched)
- Supports more iDevices than SHAtter
- Hopefully save the SHAtter bootrom exploit for future iDevices
The reason for this is bootrom exploits are not patchable with software updates. It requires new hardware to fix the security hole. Since the limera1n hole was already discovered and patched Apple, it benefits the community if SHAtter is saved in hopes of using it with new hardware, like the 5th Generation iPhone/iPod Touch and the 2nd Generation iPad.
