(adsbygoogle = window.adsbygoogle || []).push({}); Here you go guys, we have some progress which is real good news.
You must login or register to view this content.

Yeah too bad ROOT KEY= Per Console Key so You would need to dump your own key in order to decrypt your bootloader and metldr. so even if they get it its only for their console.

True, But maybe they can release a .pkg that would let you do it for your own

Just wondering, if they get the metldr then we don't need to decrypt our Root Key, right??? Because if you have the metldr they have the ability to make a 3.66 CFW, if not they can release this method and a dev can use the information to make a CFW, right???? I am just wondering, but if the metldr isn't enough then can the information in the bootloader and the metldr be enough???? Thanks

---------- Post added at 12:42 AM ---------- Previous post was at 12:39 AM ----------



Correct me if I am wrong, but to dump the NAND, you have to solder something on the PS3. If I am wrong, please correct me because I think that a simple .pkg isn't enough to dump the NAND same with the NOR. I think you need an infectus for that. If I am wrong, I accept that, just my 2 cents. Thanks

Hope your wrong because I don't trust myself to solder my PS3 ahaha.

Im going to explain this as easy as possible for you There are 2 very different types of keys at work here... and there are multiple different values of these 2 keys for different parts of the system.

First of all, the riv/erk keys are used to symmetrically encrypt executables using a AES-CTR cipher, and the key for this on the metldr is what is referred to as the "root key", because every other key can be discovered by following down this chain and decrypting each level firmware and its loader (lv0, lv1, etc).

Secondly, the public/private keypair is used only to digitally sign the hash of the executable. Each loader effectively checks the signature of the "loader" (lv1, lv2, game, etc) to ensure that it is officially authorized by Sony. The current private components of these keys were compromised during Sony's failure to understand "randomness" allowing us to digitally sign new firmware, executables, etc.

So to answer your question We already have the metldr key, the thing is that they don’t use metldr anymore, at all.Sony removed all the loaders, no more isoldr/lv1ldr/lv2ldr/appldr they added lv0.2 which seems to have secured the ps3 for now

not to be the beare of good news but the NAND and NOR are both the same for every ps3, Now the only reason why they are dumped arre to obtain "keys" among ps3 the keys are "controlled" by levels 0,1,2, Now if we are able to decrypt lv0 we are able to write any code "any" code as header doesnt check the size. So technically speaking if we dump decrypt lv0 we have full control over the ps3. Now correct me if im wrong but a script(not a real script but you gte the point) can be turned to a .pkg and that script can therefore patch the lv0 and thus not needing to dump the Nand nor as if we decrypt the lv0 we can also decrypt Sony's "Signature" (run .pkg from OFW) and thus owning the ps3 completely.. there isnt much need for nand or nor only to decrypt the lower level programming

Thanks for the quick reply and thanks for correcting me. That makes sense, I knew I was wrong. hahaha. But thanks again. But, just wondering, what's the use of what gitbrew did??? Did they decreypt lv0.2 or something, or did they simply dump the nand, which will lead to nothing??? Thanks again.

Wait, they said they dumped bootloader and I thought you said Sony took out the loaders. Then can this be an old firmware???

Your welcome and to answer your first question i dont know exactly what Gitbrews intentions for doing this are because im obviously not Gitbrew your gonna have to ask them, and about the loaders i said sony removed all of these isoldr/lv1ldr/lv2ldr/appldr.

Thats a great explanation mate. Cheers for clearing up that, can imagine a few people dont understand process that occurs with the ps3.