Developer KaKaRoToKS over de nieuwe PS3 hack

RDJ134 23 oktober 2012 om 20:22 uur

Zoals je vandaag al eerder kon lezen, is de PlayStation 3 behoorlijk hard gekraakt in de afgelopen 48 uur. Maar veel mensen boeit maar één ding en dat is het spelen van 'back up' games. Maar wat ons van Eigenwereld.nl meer interesseert is hoe dit technisch mogelijk is. Op die vraag geeft de developer KaKaRoToKS antwoord, en dat is onder andere nogal wat techno praat wat niet voor iedereen is weg gelegd.


Since the LV0 keys have now been leaked, I believe I can now share this info with you, to help out those who are trying to build their own 4.x CFW:

The NPDRM ECDSA signature in the SELF footer is checked by lv2. It first asks appldr to tell it whether or not the signature is to be checked, and appldr will only set the flag if the SELF is a NPDRM with key revision from 3.56+ (the ones without private keys). This means that the SELF files signed with the new 3.56+ keys still don't have their ecdsa checked (probably to speed up file loading).

If appldr says the ecdsa signature must be checked, then lv2 will verify it itself, and return an error if it's not correct. There are many ways to patch this check out.

Patch out the check for the key revision in appldr
Patch out the "set flag to 1" in appldr if the key revision is < 0xB
Patch out the code in lv2 that stores the result from appldr
Patch out the actual sigcheck function from lv2.
Ignore the result of the ecdsa from lv2.



Here is one of the patches (the 4th one, patching out the check function from lv2):

In memory 0x800000000005A2A8, which corresponds to offset 0x6a2a8 in lv2_kernel.elf,

Replace:
e9 22 99 90 7c 08 02 a6

With:

38 60 00 00 4e 80 00 20

This is for the 4.21 kernel (that was the latest one when I investigated this), I will leave it as an exercise to the reader to find the right offsets for the 4.25 and upcoming 4.30 kernel files.

And here's another bit of info... in 4.21 lv2, at memory address 0x800000000005AA98 (you figure out the file offset yourself), that's where lv2 loads the 'check_signature_flag' result from appldr, so if you prefer implementing method 3 above, just replace the 'ld %r0, flag_result_from_appldr' by 'ld %r0, 0' and you got another method of patching it out. Either solutions should work just the same though.

Enjoy homebrew back on 4.x CFW....

Reageer