So, if he reversed it, it's an epic achievement.
So apparently the "epic achievement HOWTO" looks like this:
1. Start SNEEK with logging enabled
2. Start Riivolution
3. Watch what happens and copy it into your own app, not bothering to understand how it works.
- Why is the return address configured (based on the IOS version/revision) if the syscall never returns after bootmii is launched?
- Why make it return 101 (a random value I picked when writing it) without bothering to check for it in the powerpc code?
- Why use the exact same random stack locations? There are approx. 400 null bytes sprayed over a wide area, plenty of options to make it not so obvious...
Riivolution doesn't even use obfuscation, reversing it is a piece of cake once the compression is taken care of. It looks like pune at least tried to use some encryption and anti-debug checks for casper but they're not hard to work around.
It's just sad he has to waste his time in doing that...
Indeed, when he could have just told me what he wanted to do and asked if I would help. We could have even pushed out a new Riivolution update, the option to load bootmii directly from the SD card was added to SVN over a year ago but there hasn't been any significant reason to do a new release.
I don't mind this app being out there. It serves a purpose and it at least has basic protection against someone poking at it to see what's going on under the hood. The only thing I have an issue with is people acting like this is somehow the holy grail of wii hacking ("This is an achievement of epic proportions!") when it's really just a direct clone of the hard work that somebody else did with a few minor tweaks added. If ninty push out an update that kills the exploit and pune manages to find some other way to keep casper alive (without just using the HBC exploit instead, which he also knows), then you can have all the backslapping, singing of praises and naming of firstborns that you want.