Ticket: Difference between revisions
Game updates are cetks, support added in 2.0.0. |
Moosehunter (talk | contribs) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 84: | Line 84: | ||
| 0x141 || 0x1 || Title key type | | 0x141 || 0x1 || Title key type | ||
|- | |- | ||
| 0x142 || | | 0x142 || 0x3 || Unknown | ||
|- | |||
| 0x145 || 0x1 || Master key revision | |||
|- | |||
| 0x146 || 0xA || Unknown | |||
|- | |- | ||
| 0x150 || 0x8 || Ticket ID | | 0x150 || 0x8 || Ticket ID | ||
| Line 90: | Line 94: | ||
| 0x158 || 0x8 || Device ID | | 0x158 || 0x8 || Device ID | ||
|- | |- | ||
| 0x160 || | | 0x160 || 0x10 || Rights ID | ||
|- | |- | ||
| 0x170 || 0x4 || Account ID | | 0x170 || 0x4 || Account ID | ||
| Line 101: | Line 103: | ||
|} | |} | ||
The title key can be stored as a 16-byte block when tickets are "common" [2.0.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. | 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. | ||