PS3 BD-Laser Revision: 0x04 (KES-400, SACD supported) PS3 Motherboard Revision: 0x0B (JTP-001 Motherboard, Revision 1) PS3 System Target ID: 0x85 (Retail - Europe) ) useful? IDPS dumping Tools PS3 Model Detection Currently looking into that, but I never worked with openCL before and can't even find a hmac/sha1 kernel for openCL. Using openCL would help, because graphic cards are naturally faster than CPUs. Moreover, I even cheated and only bruteforced the last six bytes of my (known) IDPS. But even with all optimizations (especially for C#) and running on all cores with parallelization it isn't really THAT fast. I was just looking into that and did a small PoC in c#, which BFs my IDPS. The easiest would be of course param.sfo of savedata, by manually verifying a certain sha1-hmac made from the file PARAM.PFD with idps as key. Just some thoughts from zecoxao, someone who just entered the PS3 dev scene, so don't be too harsh please ) If the scene could establish some kind of standard or bruteforce blueprint, like a blank PARAM.SFO of the PS3 singstar app, which should look the same on every console, someone could even work on a rainbow table for IDPS. I mean most of the information is known so in the best case you chose your region and model and only have to bruteforce the last six bytes (if the Chassis Check was known better). How is the current state (or former experience) with bruteforcing the IDPS from the IDPS hash of a PARAM.SFO file (second hash iirc).
Anyone have any suggestions or know of a way I could crack the IDPS used to encrypt my backup ?" I want to recover all my data to my new PS3, but need to be able to dump all the data from archive2.dat to create a fresh backup with all the data to restore to the new unit. Problem: "My old PS3 received the YLOD, however I have a hard drive backup of it, but not longer have the actual unit, but I do have a new PS3. You would need to bruteforce 7 bytes, if you could take care of all the possibilities for Chassis Check. You can verify the IDPS of a PS3 console through 2 ways : param.sfo of savedata or HDD backup from PS3. There are homebrews to dump or even spoof your PS3 IDPS. With PS3Xploit, just do a flash dump and search inside. IDPS have been successfully written to: idps.bin
It doesn’t contains any malicious code and can be safely used like any other proxy server. IDPStealer works as a proxy server and intercepts all network traffic (including SSL traffic via HTTPS over HTTP tunneling) and it tries to get IDPS from it. So please, if you want to get an IDPS from your console then do it as fast as possible because I think this method won’t work in the nearly future. It can be used to steal other people’s IDPS if you have an access to their consoles.Īnd it seems that this is the only method of getting ConsoleId without using hardware solutions on the moment.A big company will fix it in the next firmwares.However there are several cons about releasing:
It can be used on OFW/CFW firmware and you don’t need any additional software/hardware installed on your PS3.
Network (PSN connections) idpstealer.exe Bytes 13th, 14th, 15th, 16th: per console identifyer ? a hash / encryption of previous bytes ? encrypted timestamp ?Ġ.Bytes 11th and 12th: (0xFF 0xFF in the Dummy Reference Tool IDPS).It seems to be an unique identifyer, the dummy IDPS used in the reference tool PS3 models seems to indicate is composed of 2 parts: unk1, unk2 This procedure reduces the total number of posible results a lot, it seems to be a bit pointless to store the "non-bitshifted" value instead of the result of the bitshift.0xF4 > 2 gives 61 Remaining bytes seam to be an identifier generated from some per console data (Internal:Product Code) (Internal: Product Sub Code)ħth and 8th byte represent Product Sub Codeġ0th byte represents an unknown model identifier The IDPS is a sequence of 16 bytes which is used as a unique per-console Identifier.