Sry to double post, but ya the guide is up, and also to those of you that didn't see the other thread, I need a system.dreg from someone who owns a LocationFree player, and actually has it up and running on their psp.
Printable View
Sry to double post, but ya the guide is up, and also to those of you that didn't see the other thread, I need a system.dreg from someone who owns a LocationFree player, and actually has it up and running on their psp.
Ah, I was using it Incorrectly, thankyou TO!
Mines not buggy at all! A little slow, but I've tested everything and i have no errors! this is great! EDIT 1 bug, the web browser crashes.
I can feel it now, we are extremely close, now we just need to find out how to code our own font-files so that we can run our own code!
skylark, have you tried making a similar program to get the checksum for the firmware updates? It might be easy if it uses the same encryption method. Then we could use the 1.5 update as a 2.61 update, if it isn't the same checksum method, how could we find it and would this work?
Nope, firmware updates won't use the same algorithms, they use actual signing (with Sony's private keys) as opposed to merely hashing (to verify integrity).
The PSP fonts do not contain executable code by design (... I'd bet) - they are just data. What we hope for is that those data are not loaded correctly by the font file parser. Font file parsers on other machines (Xbox) have been shown to contain critically important faults.
We have probed at the registry parser itself, but it seems that Sony did a reasonably decent job on that and that it won't be readily exploitable. Which is a pity as it runs fully in kernel mode.
hmmm. so another question to the upgrade files:
are they only signed (some bytes at the end for the pub/private key process) or encrypted?
i bet encrypted.... but im not sure.
They are protected. You can not edit it without knowing their key, which is impossible to get without millions of years of brute force
well u could just as well start now then :P
Yup. The registry doesn't contain anything security-critical on itself, so Sony didn't bother. Anyway, the programmer who did the registry.prx module deserves a raise from Sony. The module is a piece of good quality code, at least at the first and second glance :(
so is that the end of this?