|
The iPhone Wiki is no longer updated. Visit this article on The Apple Wiki for current information. |
Difference between revisions of "Talk:AT+FNS"
(→What commands did Apple remove?: new section) |
|||
| Line 6: | Line 6: | ||
It was already closed in 3.1b1, thanks to NitroKey (but it was available in 3.0). Interestingly, NitroKey posted their hashes the next day after I found it. Anyway, it doesn't really matter as Apple would have removed it anyway (AT+FNS isn't used by the iPhone itself). --[[User:Oranav|oranav]] 05:13, 28 August 2009 (UTC) |
It was already closed in 3.1b1, thanks to NitroKey (but it was available in 3.0). Interestingly, NitroKey posted their hashes the next day after I found it. Anyway, it doesn't really matter as Apple would have removed it anyway (AT+FNS isn't used by the iPhone itself). --[[User:Oranav|oranav]] 05:13, 28 August 2009 (UTC) |
||
| + | |||
| + | == What commands did Apple remove? == |
||
| + | |||
| + | Did the remove every single command that nucleus doesn't use? Can nearly every command that crashes the baseband can be used as an injection vector? If so why don't we try every single command combination left for future updates that might not be compatible with the current baseband we are using with 3.0 |
||
Revision as of 21:56, 28 August 2009
If the leaked-exploit was still in 3.1b3, why hasn't the jailbreak community assembled with pitchforks around Nitrokey? Iemit737 23:19, 27 August 2009 (UTC)
Because we aren't 4chan --geohot 23:41, 27 August 2009 (UTC)
First off it was leaked awhile ago but not many people knew about it, second off, I am pretty sure it was closed earlier anyway. ChronicDev 23:42, 27 August 2009 (UTC)
It was already closed in 3.1b1, thanks to NitroKey (but it was available in 3.0). Interestingly, NitroKey posted their hashes the next day after I found it. Anyway, it doesn't really matter as Apple would have removed it anyway (AT+FNS isn't used by the iPhone itself). --oranav 05:13, 28 August 2009 (UTC)
What commands did Apple remove?
Did the remove every single command that nucleus doesn't use? Can nearly every command that crashes the baseband can be used as an injection vector? If so why don't we try every single command combination left for future updates that might not be compatible with the current baseband we are using with 3.0
