303
edits
Changes
Jump to navigation
Jump to search
Line 19:
Line 19: +
signing bug was definitely fixed in v4
::::::1) i thought BC booted boot2, however no bootmii/mini logging is thrown at my USBGecko when booting a GC game. mini indeed has that piece of code, but its not doing the gecko_printf so mini is never started (or it is suppressed?)
::::::1) i thought BC booted boot2, however no bootmii/mini logging is thrown at my USBGecko when booting a GC game. mini indeed has that piece of code, but its not doing the gecko_printf so mini is never started (or it is suppressed?)
::::::2) when shutting down it does boot (as seen by bootmii booting up) and that somehow kills some kind of flag MIOS sets up. i always thought the bootstate told SM that it was shutting down, but something else is also going on. does BC boot mios directly? --[[User:DacoTaco|DacoTaco]] ([[User talk:DacoTaco|talk]]) 09:26, 2 May 2021 (CEST)
::::::2) when shutting down it does boot (as seen by bootmii booting up) and that somehow kills some kind of flag MIOS sets up. i always thought the bootstate told SM that it was shutting down, but something else is also going on. does BC boot mios directly? --[[User:DacoTaco|DacoTaco]] ([[User talk:DacoTaco|talk]]) 09:26, 2 May 2021 (CEST)
:::::::I can now confirm that BC did have the signing bug and it was fixed in v4; the function that checks the signature can be found by looking for the hex constant 0x000ac004 in memory, and then looking at either of the two function calls with that value as a parameter (both of which just call another function that does the actual check). In v2, there's a call to strncmp at ffff2236. In later versions, they do the comparison directly (at around ffff0fd2 (v4) or ffff0fca (v5, v6)). I'm still not sure what it's actually checking the signature ''of''; figuring that out would require a deeper understanding of the way NAND is laid out I think. --[[User:Pokechu22|Pokechu22]] ([[User talk:Pokechu22|talk]]) 22:26, 2 May 2021 (CEST)