6,263
edits
Changes
Jump to navigation
Jump to search
Line 57:
Line 57: − + Line 87:
Line 87: + + + + + + + + +
→FIRM Process9
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.
| New3DS keyXs generation
| New3DS keyXs generation
| [[9.5.0-22|9.5.0-X]]
| Mostly fixed with [[9.5.0-22|9.5.0-X]], see description.
|
|
| 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)
| [[9.3.0-21|9.3.0-X]]
| [[9.3.0-21|9.3.0-X]]
| 2012
| 2012
| [[User:Yellows8|Yellows8]]
|-
| [[AMPXI:ExportDSiWare]] export path
| Process9 allocates memory on Process9 heap for the export path then verifies that the actual allocated size matches the input size. Then Process9 copies the input path from FCRAM to this buffer, and uses it with the Process9 FS openfile code, which use paths in the form of "<mountpoint>:/<path>".
Process9 does not check the contents of this path at all before passing it to the FS code, besides writing a NUL-terminator to the end of the buffer.
| Exporting of DSiWare to arbitrary Process9 file-paths, such as "nand:/<path>" etc. This isn't really useful since the data which gets written can't be controlled.
| None
| [[9.5.0-22]]
| April 2013
| [[User:Yellows8|Yellows8]]
| [[User:Yellows8|Yellows8]]
|-
|-