68w ago - Following up on the previous update, this weekend Spanish PlayStation 3 developer Calantra has released a homebrew application to find PS3 Keys dubbed Lv0 Assault followed by updated versions below.
To quote, roughly translated: LV0 assault is an application that uses the contents of any file type to search for valid cryptographic keys to decrypt files encrypted with keys LV0 metldr * or *.
What it does:
The operation of this program is not based on the use of the techniques of "brute force" is limited to just keep trying all possible keys of 32 bytes that can be found in a file.
We can get:
If by chance the key LV0 appear in theory you could decrypt the file LV0 content updates and versions higher than 3.56 contain changes which in turn contain the long-awaited keys.
That does not do:
It is used to decrypt any file type.
It serves to create any CFW.
There used to play GT5 and to play for PSN.
If we find the key delv0 ideally, the most dense file-level data as possible, these files are those that are compressed or encrypted. It is also very useful for finding keys if you have memory dumps from the localstore.
It should be clear that it is extremely difficult and unlikely to get the key LV0 by this method, but it's better than sitting in front of the screen waiting for the prophet down the mountain with the solution to your problems. The more people looking the better.
This program is experimental and is based on a complete utility that I used some time to locate and catalog keys. There are more explanations in the file "readme" that comes with the program and contact addresses.
How to use:
Click on menu "search for" select the lv0 to find lv0 key, metldr to find metldr key.
Al the ps3devwiki contributors, Team Fail0verflow, Kakarotoks, at all of them for share their knowledges
Last of all, execuse me a lot for my bad english.
Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter and be sure to drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene updates and homebrew releases!
The xbox 360 security is a lot less complicated than the ps3. The days of say PS1 where it was so simple as to inject "SCEASCEESCEJ" over and over between the drive and the cpu (one each of the magic letters for each region that the drive read from the subchannel data on original cds), or the ps2 days where it was more complicated but once it was done there was no such thing as firmware upgrades are gone... this is where it is now for ps3...
I don't think anyone who has replied thus far has actually read what the author wrote. He said this does NOT use a bf method. If I understand it correctly, he's using all possible combinations of 32-bytes that can be found in the source file. The time required to calculate that isn't much at all. Of course, this would require the lv0 key to just be sitting there unencrypted, so pretty unlikely, but I guess one can dream. Maybe a good enhancement (for the sake of completeness) would be to first try decrypting using all known keys and then searching for lv0 key.
Either way though, I can't think of any reason lv0 key would be in any file but I guess you never know. Nobody would have expected Sony to use the same "random" key in their signing algorithm either, but as it turned out they did and all someone had to do was look.