74
edits
Changes
Jump to navigation
Jump to search
Line 84:
Line 84: − + + + + + Line 90:
Line 94: − + − |- − | 0x168 || 0x8 || Unknown Line 101:
Line 103: − + − − CommonETicket (or cetk) no longer exist. Line 119:
Line 119: − +
→Ticket data
| 0x141 || 0x1 || Title key type
| 0x141 || 0x1 || Title key type
|-
|-
| 0x142 || 0xE || Unknown
| 0x142 || 0x3 || Unknown
|-
| 0x145 || 0x1 || Master key revision
|-
| 0x146 || 0xA || Unknown
|-
|-
| 0x150 || 0x8 || Ticket ID
| 0x150 || 0x8 || Ticket ID
| 0x158 || 0x8 || Device ID
| 0x158 || 0x8 || Device ID
|-
|-
| 0x160 || 0x8 || Title ID
| 0x160 || 0x10 || Rights ID
|-
|-
| 0x170 || 0x4 || Account ID
| 0x170 || 0x4 || Account ID
|}
|}
The title key can be encrypted as a single AES block when title key type is 0 (presumably AES-128-CBC) or as an RSA-2048 message when title key type is 1. The latter is used for titles requiring stronger licensing (applications, add-on content), while the former (old) method is used for patches.
The title key can be stored as a 16-byte block when tickets are "common" [2.0.0+] with title key type 0, or as a "personalized" RSA-2048 message when title key type is 1. The latter is used for titles requiring stronger licensing (applications, add-on content), while the former (old) method is used for patches.
When RSA is used, this uses an SPL key handle that is initialized with the console-unique RSA-2048 ticket key.
When RSA is used, this uses an SPL key handle that is initialized with the console-unique RSA-2048 ticket key.
== Certificate chain ==
== Certificate chain ==
| XS00000021
| XS00000021
| ?
| ?
| Used to verify ticket signatures using RSA title key block
| Used to verify ticket signatures using RSA title key block ("personalized" tickets)
|-
|-
| Ticket
| Ticket