Ok, I have been around the scene for awhile... in the background. Searching and soaking up all the information that I can.
And after reading this article about the details behind the 007 save game hack and how it actually works.
Click here to read articleI realized that we still need the "key" to be able to sign other apps to work with this exploit. Because as most of you including myself have noticed, the font signature doesn't work when signing anything, including evox.
After reading the above article, this is what happens...
The buffer overflow happens, "... It then disables write protection in the kernel memory. It then proceeds to scan through RAM, looking for the last four bytes of the
public key. Once it finds that, it modifies the last four bytes of the public key. Once you modify the public key this way, you end up with a public key that is easily factorable. It is now divisible by 3! This allows us to easily figure out the other prime, and from that then we can recreate the secret key used. "
So we need to figure out how this particular overflow works, and then figure out if it uses the same method as the 007 hack by changing the last 4 bytes of the signature.
hrm... has anyone tried signing evox(which you have to rename linux.xbe) with the 007 signature and testing to see if it loads?
I might have to try this to see if they just copied that part of the code...
I am at work now I will try it once I get home.
We need to work as a team to figure this out. Those this MAY mess up peoples abilities to listen to music while playing games, it seems like the way to go until the
issues with the font exploit are resolved.
I will keep you all posted. Also any that knows different please correct me if I am wrong about anything I have stated.
CP