|
The iPhone Wiki is no longer updated. Visit this article on The Apple Wiki for current information. |
Difference between revisions of "NitroKey"
m |
|||
| (7 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | '''NitroKey''' was a product released in late {{date|2009|02}}, by the company "NitroKey," in order to aid those with a tethered jailbroken [[N72AP|iPod touch (2nd generation)]] to boot their iPods. It consisted of a small dongle that looked EXACTLY like the end of an iPod cable, with no cord on it. The product was being sold for an outrageous price of $55.00 to those unfortunate enough to have made the decision to purchase one, as it went obsolete within two weeks after its release. |
|
| − | They also released a |
+ | They also released a stolen version of the [[0x24000 Segment Overflow]], the vulnerability that the untethered [[N72AP|iPod touch (2nd generation)]] jailbreak uses, giving Apple enough time to fix the [[N18AP|iPod touch (3rd generation)]] so that it CAN NOT be directly jailbroken from its release. In addition, NitroKey's irresponsible handling gave Apple enough time to add the [[ECID]] tag to the [[IMG3 File Format]] in the [[N88AP|iPhone 3GS]], preventing a permanent untethered [[jailbreak]] without a new [[iBoot]] exploit in every firmware. |
| − | NitroKey has also leaked [[AT+FNS]], a [[baseband]] hole which was meant to be kept secret. [http://nitrokey.com/Hash.html] The hash was posted by NitroKey one day after [[User:Oranav|Oranav]] found and shared the exploit with the [[iPhone Dev Team]], making things very suspicious. Apple has now patched the hole, needlessly burning an exploit that could have been used as an unlock vector for a future firmware. |
+ | NitroKey has also leaked [[AT+FNS]], a [[Baseband Device|baseband]] hole which was meant to be kept secret. [http://nitrokey.com/Hash.html] The hash was posted by NitroKey one day after [[User:Oranav|Oranav]] found and shared the exploit with the [[iPhone Dev Team]], making things very suspicious. Apple has now patched the hole, needlessly burning an exploit that could have been used as an unlock vector for a future firmware. |
| − | |||
| − | May the thieving bastards of NitroKey burn in hell for all eternity. Their selfish leaks have done nothing short of hold the entire Jailbreak community backwards in the name of pure selfish desires. For this, the actions of NitroKey are condemned, with the suggestion they exercise sincere moral introspection before continuing their inconsiderate and obtuse line of action. |
||
| − | The Jailbreak community has always kept the interests of the public and developers as the foremost topic on their agenda. NitroKey stand as a damning symbol against this, and for these reasons, we ask you all to stand with us and shout: '''SCREW NITROKEY'''. |
||
Latest revision as of 23:14, 16 September 2021
NitroKey was a product released in late February 2009, by the company "NitroKey," in order to aid those with a tethered jailbroken iPod touch (2nd generation) to boot their iPods. It consisted of a small dongle that looked EXACTLY like the end of an iPod cable, with no cord on it. The product was being sold for an outrageous price of $55.00 to those unfortunate enough to have made the decision to purchase one, as it went obsolete within two weeks after its release.
They also released a stolen version of the 0x24000 Segment Overflow, the vulnerability that the untethered iPod touch (2nd generation) jailbreak uses, giving Apple enough time to fix the iPod touch (3rd generation) so that it CAN NOT be directly jailbroken from its release. In addition, NitroKey's irresponsible handling gave Apple enough time to add the ECID tag to the IMG3 File Format in the iPhone 3GS, preventing a permanent untethered jailbreak without a new iBoot exploit in every firmware.
NitroKey has also leaked AT+FNS, a baseband hole which was meant to be kept secret. [1] The hash was posted by NitroKey one day after Oranav found and shared the exploit with the iPhone Dev Team, making things very suspicious. Apple has now patched the hole, needlessly burning an exploit that could have been used as an unlock vector for a future firmware.
