4,620
edits
Changes
Jump to navigation
Jump to search
Line 35:
Line 35: − + − + Line 58:
Line 58: + + + + + + + + + + + + + + + + + + + + + +
→Boot Partitions
|-
|-
| 0x180000
| 0x180000
|
| 0x4000
| Keyblob area, the first 0xB0 is identical to the console-unique "customer data" section in BCTs
| Keyblob area
|-
|-
| 0x184000
| 0x184000
| Title 010000000000081A "package1" (Backup)
| Title 010000000000081A "package1" (Backup)
|}
|}
=== Keyblob ===
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0xB0
| Actual keyblob
|-
| 0xB0
| 0x150
| Unused, all-zero.
|}
The data at 0x180000 is an array of 0x200-byte entries, with a total of 32 entries. Therefore, there's 32 different keyblobs are stored here. The raw data for each one is unique compared to the others.
The 0xB0-byte keyblob is installed to the console-unique "customer data" section in BCTs(BCT+0x450), which is what gets used during system boot.
Which keyblob is loaded from here during install is presumably somewhere in BCT? <v3.0 use index0, v3.0 uses index1. Hence, the installed keyblob was changed with v3.0.
== User Partitions ==
== User Partitions ==