By entering this site you need to consent to the use of cookies and their functional use according to this privacy policy. Cookies help us to provide the functional services of the website. Kindly read the below message of use and consent to the use.
The following cookies are stored and shared when accessing this website:
- Internal cookies for the MediaWiki site. This is used for user authentication and article modifications.
- Third-party cookies from Google providing services for Google AdSense and Google Analytics
We will never use data collected outside of the above scope.
| Keyblob area, the first 0xB0 is identical to the console-unique "customer data" section in BCTs
+
| Keyblob area
|-
|-
| 0x184000
| 0x184000
Line 58:
Line 58:
| 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.