3DS System Flaws: Difference between revisions
| Line 63: | Line 63: | ||
This means that any ARM9 code that can execute before the loader clears the keyslot at firmlaunch(including firmlaunch-hax) can get access to the uncleared keyslot 0x11, which then allows one to generate all <=v9.5 New3DS keyXs which are generated by keyslot 0x11. | This means that any ARM9 code that can execute before the loader clears the keyslot at firmlaunch(including firmlaunch-hax) can get access to the uncleared keyslot 0x11, which then allows one to generate all <=v9.5 New3DS keyXs which are generated by keyslot 0x11. | ||
Therefore, to completely fix this the loader would have to generate more keys using different keyslot 0x11 keydata. | Therefore, to completely fix this the loader would have to generate more keys using different keyslot 0x11 keydata. This was done with [[9.6.0-24|9.6.0-X]]. | ||
| New3DS keyXs generation | | New3DS keyXs generation | ||
| Mostly fixed with [[9.5.0-22|9.5.0-X]], | | Mostly fixed with [[9.5.0-22|9.5.0-X]], completely fixed with new keys with [[9.6.0-24|9.6.0-X]]. | ||
| | | | ||
| February 3, 2015 (one day after [[9.5.0-22|9.5.0-X]] release) | | February 3, 2015 (one day after [[9.5.0-22|9.5.0-X]] release) | ||