Adduc
December 2nd, 2005, 04:43
I'm not a coder in the PSP community, so I don't possess the knowledge that you developers do, but I've got a question concerning the way EBOOTs are loaded.
Around August, when people were still actively trying to hack FW 1.5x to run homebrew, I read somewhere that in the 1.5x firmware and up the PSP checks for authenticated keys in the EBOOT before it executes any code. At the time, they couldn't crack the code because code needed to be run first to be able to find the code using brute force cracking. It was my understanding that the code was either 64 or 128 bit encoded.
Now that 2.0 has been hacked, could it be possible to run the code to figure the key? Would that key theoretically allow complete use of the 2.0 firmware to the extent that 1.0 and 1.5 has?
If this is a misconception, please take the time to correct me. I'd like to know what the encrpytion and security is.
Thank you.
Around August, when people were still actively trying to hack FW 1.5x to run homebrew, I read somewhere that in the 1.5x firmware and up the PSP checks for authenticated keys in the EBOOT before it executes any code. At the time, they couldn't crack the code because code needed to be run first to be able to find the code using brute force cracking. It was my understanding that the code was either 64 or 128 bit encoded.
Now that 2.0 has been hacked, could it be possible to run the code to figure the key? Would that key theoretically allow complete use of the 2.0 firmware to the extent that 1.0 and 1.5 has?
If this is a misconception, please take the time to correct me. I'd like to know what the encrpytion and security is.
Thank you.