I was just reminded of this piece that I wrote ten years ago now. It is still just as relevant today as it was back then. If you are working on any kind of reverse engineered product for hardware, learn how to care about your users to keep them safe.https://marcan.st/2011/01/safe-hacking/ …
-
-
That one near miss was a bug in this stuff in some corner case Wiis, which ended up corrupting one of the (eventual) main copies. However, my code checked and refused to run if *any* copy was not valid, so the affected user could do no further damage. Their Wii was fine.
Show this thread -
All they saw was a first install attempt (I forget if it failed or reported success) that didn't work in practice, followed by all subsequent install attempts failing with a safety check error. After fixing the bug I added even more paranoia to make sure it didn't happen again.
Show this thread
End of conversation
New conversation -
-
-
What was the novel trick?
-
I abuse the way they do bad block lists for the boot area so I can write my patched boot code to free blocks, then in one final write mark the original first copy's blocks as bad so my copy becomes the first copy. Uninstallation then is just erasing that.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.