Talk:Virtual TRM Manager: Difference between revisions

From PS3 Developer wiki
Jump to navigation Jump to search
(Created page with "== Root Info == Obtainable with packet_id 0x2014 through syscall 862. Structure is as follows: {| class="wikitable" |- ! Offset !! Size !! Description |- |0x00||0x04||unk1 ...")
 
No edit summary
Line 8: Line 8:
! Offset !! Size !! Description
! Offset !! Size !! Description
|-
|-
|0x00||0x04||unk1
|0x00||0x04||unk1||
|-
|-
|0x04||0x08||padding
|0x04||0x08||padding||
|-
|-
|0x0C||0x04||unk2
|0x0C||0x04||unk2||
|-
|-
|0x10||0x04||padding
|0x10||0x04||padding||
|-
|-
|0x14||0x04||hash_id?(goes 01 first) || 90 01
|0x14||0x04||hash_id?(goes 01 first) || 90 01
|-
|-
|0x18||0x04||padding
|0x18||0x04||padding||
|-
|-
|0x1C||0x04||hash_id?(goes 00 last) || 90 00
|0x1C||0x04||hash_id?(goes 00 last) || 90 00

Revision as of 13:42, 30 March 2014

Root Info

Obtainable with packet_id 0x2014 through syscall 862. Structure is as follows:


Offset Size Description
0x00 0x04 unk1
0x04 0x08 padding
0x0C 0x04 unk2
0x10 0x04 padding
0x14 0x04 hash_id?(goes 01 first) 90 01
0x18 0x04 padding
0x1C 0x04 hash_id?(goes 00 last) 90 00
0x20 0x08 padding
0x28 0x08 auth_id_1 10 70 00 00 02 00 00 01
0x30 0x08 auth_id_2 10 70 00 03 FF 00 00 01
0x38 0x14 srh <-root hash
0x4C 0x04 padding
0x50 0x14 srk <-root hsec
0x64 0x1C padding

Notes about root info

  • Name of packet id is "Backup SRK SRH". However, SRH shows first and SRK shows last. That seems to be denoted by the hash_ids (i decided to call them that way). auth_id_1 seems to be correlated with srk (since srk is used on VTRM, and the 0FACE0FF DEADFACE area is located after cVTRM) while auth_id_2 seems to be correlated with srh.
  • As for the unknowns, they seem to be not involved at all with the hashes, although they might have something to do with the clock drift.