Editing IDPS

The IDPS is a 16 bytes value that contains console specific information.

= Description =

The IDPS is a sequence of bytes which is used as a unical per-console Identifier. The IDPS is stored and certified in [[Flash:Encrypted Individual Data - eEID|EID]].

= Structure =

<pre>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Chassis Check
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&dArr;&nbsp;                    
00000000  00 00 00 01 00 89 00 0B 14 00 EF DD CA 25 52 66  .....‰....ïÝÊ%Rf
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&uArr;&nbsp;&uArr;&nbsp;&nbsp;&nbsp;&uArr;&nbsp;&uArr;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Product Code&nbsp;&nbsp;Model type
&nbsp;&nbsp;&nbsp;&nbsp;(Internal:Product Code)&nbsp;&nbsp;&nbsp;(Internal: Product Sub Code)
</pre>

5th and 6th byte represent [[Product Code]].

7th and 8th byte represent [[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//-->

9th byte represents <abbr title="To convert it to chassis revision, right shift it by 2 : (0x14 &gt;&gt; 0x2) = 5">chassis check</abbr>

10th byte represents an unknown model identifier

remaining bytes seam to be an identifier generated from some per console data

<pre>
00 00 00 01 <- Magic
00 89 <- CECH-xx02 Product Code (CEX target, oceania region)
00 0B <- CECH-25xx Product Sub Code (25xx series)
14 <- Chassis Check
00 <- unk0 (counter ?)
EF DD <- unk1
CA 25 52 66 <- unk2
</pre>

== Dummy Reference Tool IDPS ==

<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 when some Reference Tool PS3's IDPS fails to be decrypted from flash. That IDPS belongs to a Reference Tool DECR-1000A. The Reference Tool IDPS from above is static. aim_iso uses it. Retail/3.55 doesn't have it.

Source: [http://rmscrypt.wordpress.com/2011/05/16/idps-what-the-hell-is-that-thing/ rms' blogtext].

<pre>
00 00 00 01 <- Magic
00 81 <- Reference Tool Product Code
00 01 <- DECR-1000/TMU-520 Product Sub Code
03 <- Chassis Check
FF <- unk0 (dummy)
FF FF <- unk1 (dummy)
18 43 C1 4D <- unk2
</pre>

== Dummy PSP Emulator IDPS ==

<pre>0x00, 0x00, 0x00, 0x01, 0x00, 0x81, 0x00, 0x01, 0x0C, 0x40, 0x00, 0xB1, 0x0E, 0x69, 0x69, 0x78</pre>

Found into the emulator_drm.sprx (iso self inside).

== Chassis Check ==

The Chassis Check seems to be still a secret, or at least it's not 100% clear what it represents. According to the analysis of many different models of PSP, PS3, PSVita and PS4, it is clear that the only possible values are:<br>
*0x3 in PS3 reference tool dummy IDPS only
*0x4
*0xC in PSVita only ? (never found in PS3)
*0x10
*0x14
*0xF4
*0x90 in PSVita only ? (never found in PS3)

<s>We clearly see that most of PS3 models released at the same period have the same Chassis Check, and that the more the console is released late, the more high the Chassis Check is.</s><br>
In the PS3 every PS3 model/motherboard seems to start with 0x04 (ie: we have reports of COK-001, SEM-001, DIA-001, DIA-002, VER-001, JTP-001/JSD-001, all them with 0x0400), but we also have reports of the same motherboards with higher values, see [[Talk:IDPS|talk page]]
<abbr style="color:red">'''Speculation''': That increase of the value could be related with the production dates, or could be an identifyer of the factory where it was produced, or other stuff like that directly related with the production</abbr>

*Chasis check speculation (bytes 9th and 10th):
**9th byte (most common: 0x04, 0x10, 0x14, 0xF4), or 0x03 in the PS3 Reference Tool dummy IDPS
***First [https://en.wikipedia.org/wiki/Nibble nibble] values: 0, 1, or F
***Second [https://en.wikipedia.org/wiki/Nibble nibble] values: 0, 4, or 3 in the PS3 Reference Tool dummy IDPS
**10th byte (seems to be a counter, biggest value found 0x22), 0xFF in the PS3 Reference Tool dummy IDPS, 0x40 in the PSP dummy IDPS
***First [https://en.wikipedia.org/wiki/Nibble nibble] values: 0, 1, or 2
***Second [https://en.wikipedia.org/wiki/Nibble nibble] values: too random to find a pattern

=== Right shifting theory ===
Doing [https://en.wikipedia.org/wiki/Arithmetic_shift right shift] by 2 results in:
*0x3 >> 2 gives 0
*0x4 >> 2 gives 1
*0xC >> 2 gives 3
*0x10 >> 2 gives 4
*0x14 >> 2 gives 5
*0xF4 >> 2 gives 61 <-- that's an exception, in the [[Talk:IDPS|talk page]] there are 4 reports using 0xF4, only one of them is marked as refurbished


*Critics:
**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

== Last 6 bytes of 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[2], unk2[4]
*Bytes 11th and 12th: (0xFF 0xFF in the Dummy Reference Tool IDPS)
*Bytes 13th, 14th, 15th, 16th: per console identifyer ? 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 =

== NAND/NOR ==

The IDPS can be found in EID0 and EID5. See [[Flash:Encrypted_Individual_Data_-_eEID#EID0|Flash]] (NAND @ 0x80870 / NOR @ 0x2F070).

== registry? ==

?It can also be found in registry/application_persistent file inside playstation Store folder (as DeviceID)?

== 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: [https://dl.dropboxusercontent.com/u/35197530/zip/idpstealer.7z 1], or [https://web.archive.org/web/20160309135920/http://pastie.org/private/wlakfucps3bc21dfuosdtg 2]

<div style="border-width: 1px; border-style:dashed; border-color:#000000; padding: 10px; background-color:#FFFFFF; color:#000000; ">
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.
</div>

 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

= Changing IDPS =

Theory: If you give a slim console a fat IDPS, would that console have 3.15 OtherOS functionality?

I would say it would, because most likely the check is done in firmware to either en/disable that option. However, it would still require a console that can be downgraded to that version (only CECH-20xx/DYN-001, because CECH-21xx/SUR-001 use different drivers for RSX). So classic OtherOS on a CellBE 45nm/RSX 40nm would be impossible (of course you can use OtherOS++).

= 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. You would need to bruteforce 7 bytes, if you could take care of all the possibilities for Chassis Check.

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. 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. Anyone have any suggestions or know of a way I could crack the IDPS used to encrypt my backup ?"

How is the current state (or former experience) with bruteforcing the IDPS from the IDPS hash of a PARAM.SFO file (second hash iirc). 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). 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. Just some thoughts from zecoxao, someone who just entered the PS3 dev scene, so don't be too harsh please ;)

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. I was just looking into that and did a small PoC in c#, which BFs my IDPS. But even with all optimizations (especially for C#) and running on all cores with parallelization it isn't really THAT fast. Moreover, I even cheated and only bruteforced the last six bytes of my (known) IDPS. It's currently still running xD. Using openCL would help, because graphic cards are naturally faster than CPUs. Currently looking into that, but I never worked with openCL before and can't even find a hmac/sha1 kernel for openCL. Like nobody every did that before ... ;) [https://searchcode.com/codesearch/view/45893397/ useful?]

= Tools =

== PS3 Identification tools ==

=== Multiman ===

IDPS is displayed under setting information in MultiMan.

=== [Homebrew-App] PS3 Model Detection ===

Source: http://www.ps3hax.net/2011/01/homebrew-app-ps3-model-detection/]

<pre>
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
</pre>

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.

=== [Homebrew-App] IDPS Viewer ===

Source [http://www.tortuga-cove.com/hacking/31-ps3/8396-released-idps-viewer link]

* Displays the IDPS
* Shows Product Code
* Displays Motherboard revision
* Save IDPS (16 bytes from EID) into dev_hdd0/IDPS.bin file


{{Flash}}
{{Development}}<noinclude>[[Category:Main]]</noinclude>