IDPS: Difference between revisions
Jump to navigation
Jump to search
CelesteBlue (talk | contribs) (Updated with official names and verified information) |
|||
| Line 1: | Line 1: | ||
= Description = | = Description = | ||
The IDPS is a sequence of 16 bytes which is used as a unique per-console | |||
The IDPS is a sequence of 16 bytes which is used as a unique per-console identifier for PlayStation consoles. The IDPS is stored and certified in [[Flash:Encrypted Individual Data - eEID|EID]]. | |||
= Structure = | = Structure = | ||
<pre> | <pre> | ||
00000000 00 00 00 01 00 89 00 0B 14 00 EF DD CA 25 52 66 .....‰....ïÝÊ%Rf | 00000000 00 00 00 01 00 89 00 0B 14 00 EF DD CA 25 52 66 .....‰....ïÝÊ%Rf | ||
⇑ ⇑ ⇑ ⇑ | ⇑ ⇑ ⇑ ⇑ | ||
Product Code | Product Code Product Sub Code | ||
</pre> | </pre> | ||
5th and 6th | * 1st and 2nd bytes represent the magic (always 00 00) | ||
* 3rd and 4th bytes represent the Company (usually SCE) | |||
* 5th and 6th bytes represent the [[Product Code]] | |||
* 7th and 8th bytes represent the [[Product Sub Code]] <!--// Note that CECHAxx is type 0x01 and CECHBxx is type 0x02 but they both have a COK-001 motherboard... (Changing 0x02 to 0x01 in CECH-B will enable wifi options in menu. But there is still missing hardware), and at the opposite... CECH-25xx models are type 0x0B but with 2 possible motherboards: JSD-001 or JTP-001//--> | |||
* remaining 8 bytes are parsed by bits not by bytes (see [[IDPS#IDPS second half]]) | |||
<pre> | |||
00 00 <- Unknown | |||
00 01 <- Company (SCE) | |||
00 89 <- Product Code: PS3, CEX, oceania | |||
00 0B <- Product Sub Code: CECH-25xx (25xx series) | |||
14 00 EF DD CA 25 52 66 <- Second half: factory code 5, no Ps Flag, serial number 61405, random stamp CA 25 52 66 | |||
</pre> | |||
== Dummy PSP IDPS in Kicho & Dengo Program == | |||
<pre>0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x07, 0xFF, 0x03, 0xFF, 0xFF, 0xFF, 0xD7, 0xC3, 0xE5, 0x5A</pre> | |||
Found in PSP Kicho & Dengo Tool flashData.prx. | |||
== Dummy Reference Tool IDPS == | == Dummy Reference Tool IDPS == | ||
| Line 37: | Line 35: | ||
<pre>0x00, 0x00, 0x00, 0x01, 0x00, 0x81, 0x00, 0x01, 0x03, 0xFF, 0xFF, 0xFF, 0x18, 0x43, 0xC1, 0x4D</pre> | <pre>0x00, 0x00, 0x00, 0x01, 0x00, 0x81, 0x00, 0x01, 0x03, 0xFF, 0xFF, 0xFF, 0x18, 0x43, 0xC1, 0x4D</pre> | ||
This is the dummy IDPS that is used | This is the dummy IDPS that is used by PS3 Reference Tool aim_iso when IDPS fails to be obtained from flash. That IDPS belongs to a Reference Tool DECR-1000A. The Reference Tool IDPS from above is static. PS3 CEX 3.55 does not have it. | ||
Source: [http://rmscrypt.wordpress.com/2011/05/16/idps-what-the-hell-is-that-thing/ rms' blogtext]. | Source: [http://rmscrypt.wordpress.com/2011/05/16/idps-what-the-hell-is-that-thing/ rms' blogtext]. | ||
== Dummy PSP Emulator IDPS == | == Dummy PSP Emulator IDPS == | ||
| Line 55: | Line 43: | ||
<pre>0x00, 0x00, 0x00, 0x01, 0x00, 0x81, 0x00, 0x01, 0x0C, 0x40, 0x00, 0xB1, 0x0E, 0x69, 0x69, 0x78</pre> | <pre>0x00, 0x00, 0x00, 0x01, 0x00, 0x81, 0x00, 0x01, 0x0C, 0x40, 0x00, 0xB1, 0x0E, 0x69, 0x69, 0x78</pre> | ||
Found | Found in emulator_drm.sprx (iso self inside). | ||
== | == IDPS second half == | ||
*Byte 8 bits 0-5: factory code | |||
* | *Byte 8 bits 6-7 and byte 9 bits 0-5: Ps flags on PSP, maybe extended serial number on PS3 | ||
* | *Byte 9 bits 7-8 and bytes 10-11: serial number | ||
* | *Bytes 12-15: random stamp, a hash / encryption of previous bytes ? encrypted timestamp ? | ||
== PS3 IDPS Regex == | |||
Based on 300+ PS3 IDPS dumps | |||
<pre>0{7}10{2}8[456789ACE]000[6789ABCD][01F][04][0123][0123456789ABCDEF]{13}</pre> | |||
= Location = | = Location = | ||
== | == Serial flash == | ||
The IDPS can be found in EID0 and EID5. See [[Flash:Encrypted_Individual_Data_-_eEID#EID0|Flash]] (NAND @ 0x80870 / NOR @ 0x2F070). | The PS3 IDPS can be found in serial flash, precisely in EID0 and EID5. See [[Flash:Encrypted_Individual_Data_-_eEID#EID0|Flash]] (NAND @ 0x80870 / NOR @ 0x2F070). | ||
== Network (PSN connections) == | == Network (PSN connections) == | ||
=== idpstealer.exe === | === idpstealer.exe === | ||
* Patched since FW 4.70 and deprecated since ps3exploit | * Patched since FW 4.70 and deprecated since ps3exploit | ||
* This method no longer works because now Sony uses '''OpenPSID''' instead of '''IDPS''' although the key/algorithm remains the same | * This method no longer works because now Sony uses '''OpenPSID''' instead of '''IDPS''' although the key/algorithm remains the same | ||
| Line 152: | Line 109: | ||
== Bruteforce == | == Bruteforce == | ||
You can verify the IDPS of a PS3 console through 2 ways : | You can verify the IDPS of a PS3 console through 2 ways: PARAM.SFO of savedata or HDD backup from PS3 Backup Utility. You would need to bruteforce about 7 bytes, if you know the PS3 model. | ||
Problem: "My old PS3 received the YLOD, however I have a hard drive backup of it, but | Problem: "My old PS3 received the YLOD, however I have a hard disk drive backup of it, but I no longer have the actual unit, and I do have a new PS3. I want to recover all my data to my new PS3, but I need to be able to dump all the data from archive2.dat to create a fresh HDD backup with all the data to restore to my new PS3 unit. So I need to crack the IDPS used to encrypt the backup." | ||
Solution (to test) by zecoxao: "Bruteforce the IDPS from the IDPS hash of a PARAM.SFO file (second hash iirc). You select your region and model and only have to bruteforce the last six bytes. If the scene could establish some kind of standard or bruteforce blueprint, like a blank PARAM.SFO of the PS3 SingStar application, which should look the same on every console, someone could even work on a rainbow table for IDPS. The easiest would be PARAM.SFO of savedata, by manually verifying a certain sha1-hmac made from the file PARAM.PFD with IDPS as key. I was just looking into that and made a small PoC in C#, which bruteforces my PS3 IDPS. But even with all optimizations (especially for C#) and running on all cores with parallelization it is not really that fast. Moreover, I even cheated and only bruteforced the last six bytes of my known IDPS. It is currently still running... Using openCL would help, because graphic cards are naturally faster than CPUs. Currently looking into that, but I never worked with openCL before and cannot even find a hmac/sha1 kernel for openCL. Like nobody every did that before ... ;) [https://searchcode.com/codesearch/view/45893397/ useful?]" | |||
The easiest would be | |||
= IDPS dumping Tools = | = IDPS dumping Tools = | ||
== PS3 Model Detection == | == PS3 Model Detection == | ||
Source: http://www.ps3hax.net/2011/01/homebrew-app-ps3-model-detection/] | Source: http://www.ps3hax.net/2011/01/homebrew-app-ps3-model-detection/] | ||
<pre> | <pre> | ||
Dumping PS3 Model Data: | Dumping PS3 Model Data: | ||
| Line 190: | Line 147: | ||
== IDPS Viewer == | == IDPS Viewer == | ||
Source [http://www.tortuga-cove.com/hacking/31-ps3/8396-released-idps-viewer link] | Source [http://www.tortuga-cove.com/hacking/31-ps3/8396-released-idps-viewer link] | ||
* Displays the IDPS | * Displays the IDPS | ||
* Shows Product Code | * Shows Product Code | ||
| Line 196: | Line 155: | ||
* Save IDPS (16 bytes from EID) into dev_hdd0/IDPS.bin file | * Save IDPS (16 bytes from EID) into dev_hdd0/IDPS.bin file | ||
== | == multiMAN == | ||
IDPS is displayed under setting information in | |||
IDPS is displayed under setting information in multiMAN PS3 homebrew. | |||
= See also = | |||
[https://github.com/CelesteBlue-dev/PS-ConsoleId-wiki PS ConsoleId wiki by CelesteBlue] | |||
{{Flash}} | {{Flash}} | ||
{{Development}}<noinclude>[[Category:Main]]</noinclude> | {{Development}}<noinclude>[[Category:Main]]</noinclude> | ||
Revision as of 00:25, 19 May 2022
Description
The IDPS is a sequence of 16 bytes which is used as a unique per-console identifier for PlayStation consoles. The IDPS is stored and certified in EID.
Structure
00000000 00 00 00 01 00 89 00 0B 14 00 EF DD CA 25 52 66 .....‰....ïÝÊ%Rf ⇑ ⇑ ⇑ ⇑ Product Code Product Sub Code
- 1st and 2nd bytes represent the magic (always 00 00)
- 3rd and 4th bytes represent the Company (usually SCE)
- 5th and 6th bytes represent the Product Code
- 7th and 8th bytes represent the Product Sub Code
- remaining 8 bytes are parsed by bits not by bytes (see IDPS#IDPS second half)
00 00 <- Unknown 00 01 <- Company (SCE) 00 89 <- Product Code: PS3, CEX, oceania 00 0B <- Product Sub Code: CECH-25xx (25xx series) 14 00 EF DD CA 25 52 66 <- Second half: factory code 5, no Ps Flag, serial number 61405, random stamp CA 25 52 66
Dummy PSP IDPS in Kicho & Dengo Program
0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x07, 0xFF, 0x03, 0xFF, 0xFF, 0xFF, 0xD7, 0xC3, 0xE5, 0x5A
Found in PSP Kicho & Dengo Tool flashData.prx.
Dummy Reference Tool IDPS
0x00, 0x00, 0x00, 0x01, 0x00, 0x81, 0x00, 0x01, 0x03, 0xFF, 0xFF, 0xFF, 0x18, 0x43, 0xC1, 0x4D
This is the dummy IDPS that is used by PS3 Reference Tool aim_iso when IDPS fails to be obtained from flash. That IDPS belongs to a Reference Tool DECR-1000A. The Reference Tool IDPS from above is static. PS3 CEX 3.55 does not have it.
Source: rms' blogtext.
Dummy PSP Emulator IDPS
0x00, 0x00, 0x00, 0x01, 0x00, 0x81, 0x00, 0x01, 0x0C, 0x40, 0x00, 0xB1, 0x0E, 0x69, 0x69, 0x78
Found in emulator_drm.sprx (iso self inside).
IDPS second half
- Byte 8 bits 0-5: factory code
- Byte 8 bits 6-7 and byte 9 bits 0-5: Ps flags on PSP, maybe extended serial number on PS3
- Byte 9 bits 7-8 and bytes 10-11: serial number
- Bytes 12-15: random stamp, a hash / encryption of previous bytes ? encrypted timestamp ?
PS3 IDPS Regex
Based on 300+ PS3 IDPS dumps
0{7}10{2}8[456789ACE]000[6789ABCD][01F][04][0123][0123456789ABCDEF]{13}
Location
Serial flash
The PS3 IDPS can be found in serial flash, precisely in EID0 and EID5. See Flash (NAND @ 0x80870 / NOR @ 0x2F070).
Network (PSN connections)
idpstealer.exe
- Patched since FW 4.70 and deprecated since ps3exploit
- This method no longer works because now Sony uses OpenPSID instead of IDPS although the key/algorithm remains the same
- This should work also on PS4 and PSVita, but with a different key (not known/public atm)
- Download links: 1, or 2
From flatz: Privet, PS3 fans! Once KaKaRoTo published his backup tool I’ve decided to bring a way of getting a Console ID (IDPS) to the community. It can be used on OFW/CFW firmware and you don’t need any additional software/hardware installed on your PS3.
However there are several cons about releasing:
- A big company will fix it in the next firmwares.
- It can be used to steal other people’s IDPS if you have an access to their consoles.
And it seems that this is the only method of getting ConsoleId without using hardware solutions on the moment. 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.
How it works: 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. It doesn’t contains any malicious code and can be safely used like any other proxy server.
Usage: idpstealer.exe [options] <idps file> Options: -p <port number> - Port to listen on (default: 1337 -h - Show this help Arguments: <idps file> - Output file for IDPS
C:\>idpstealer.exe idps.bin Starting proxy server on 192.168.1.13:1337 IDPS have been successfully written to: idps.bin
Obtaining IDPS of a PS3
HEN
With PS3Xploit, just do a flash dump and search inside.
CFW
There are homebrews to dump or even spoof your PS3 IDPS.
Bruteforce
You can verify the IDPS of a PS3 console through 2 ways: PARAM.SFO of savedata or HDD backup from PS3 Backup Utility. You would need to bruteforce about 7 bytes, if you know the PS3 model.
Problem: "My old PS3 received the YLOD, however I have a hard disk drive backup of it, but I no longer have the actual unit, and I do have a new PS3. I want to recover all my data to my new PS3, but I need to be able to dump all the data from archive2.dat to create a fresh HDD backup with all the data to restore to my new PS3 unit. So I need to crack the IDPS used to encrypt the backup."
Solution (to test) by zecoxao: "Bruteforce the IDPS from the IDPS hash of a PARAM.SFO file (second hash iirc). You select your region and model and only have to bruteforce the last six bytes. If the scene could establish some kind of standard or bruteforce blueprint, like a blank PARAM.SFO of the PS3 SingStar application, which should look the same on every console, someone could even work on a rainbow table for IDPS. The easiest would be PARAM.SFO of savedata, by manually verifying a certain sha1-hmac made from the file PARAM.PFD with IDPS as key. I was just looking into that and made a small PoC in C#, which bruteforces my PS3 IDPS. But even with all optimizations (especially for C#) and running on all cores with parallelization it is not really that fast. Moreover, I even cheated and only bruteforced the last six bytes of my known IDPS. It is currently still running... Using openCL would help, because graphic cards are naturally faster than CPUs. Currently looking into that, but I never worked with openCL before and cannot even find a hmac/sha1 kernel for openCL. Like nobody every did that before ... ;) useful?"
IDPS dumping Tools
PS3 Model Detection
Source: http://www.ps3hax.net/2011/01/homebrew-app-ps3-model-detection/]
Dumping PS3 Model Data: - PS3 System Target ID: 0x85 (Retail - Europe) - PS3 Motherboard Revision: 0x0B (JTP-001 Motherboard, Revision 1) - PS3 BD-Laser Revision: 0x04 (KES-400, SACD supported) Probable Model: CECH-2504A Raw Model Data: Byte 0: 0x00 Byte 1: 0x01 Byte 2: 0x00 Byte 3: 0x85 Byte 4: 0x00 Byte 5: 0x0B Byte 6: 0x00 Byte 7: 0x04
Notes:
- '7th byte of IDPS' is not Bluray Drive (it was misunderstood at that time). You can see it in the example where it names incorrectly a CECH-25xx as Super Audio CD compatible with a KES-400 laserslide (which in real life has either KES-460A or KES-470A without daughterboard (swap can be done without remarry).
- Also, it named bytes 0-2 "Byte 0", byte 3 "Byte 1", byte 4 "Byte 2", byte 5 "Byte 3", byte 6 "Byte 4", byte 7 "Byte 5", byte 8 "Byte 6", byte 9 "Byte 7" etc.
IDPS Viewer
Source link
- Displays the IDPS
- Shows Product Code
- Displays Motherboard revision
- Save IDPS (16 bytes from EID) into dev_hdd0/IDPS.bin file
multiMAN
IDPS is displayed under setting information in multiMAN PS3 homebrew.
See also
PS ConsoleId wiki by CelesteBlue
| |||||||||||||||||||||||||||||||||||||||||||||
