CommonETicket: Difference between revisions
No edit summary |
|||
| Line 16: | Line 16: | ||
| 0x004||0x100||Signature | | 0x004||0x100||Signature | ||
|- | |- | ||
| 0x104||0x3C||Padding | | 0x104||0x3C||Signature Padding, aligning end of signature to 0x40 bytes | ||
|- | |- | ||
| 0x140||0x40||Issuer | | 0x140||0x40||Issuer | ||
| Line 51: | Line 51: | ||
|} | |} | ||
The Signature Type is the same const as that in [[TMD]]. | The Signature Type is the same const as that in [[TMD]]. | ||
The titlekey is decrypted by using the [[AES]] engine with the ticket common-key keyslot where the keyY is one of 6 keyYs loaded via the keyY index stored in the ticket. AES-CBC mode is used where the IV is the big-endian titleID. Note that on a retail unit index0 is a retail keyY, while on a dev-unit index0 is the dev common-key which is a normal-key.(On retail for these keyYs, the hardware key-scrambler is used) | The titlekey is decrypted by using the [[AES]] engine with the ticket common-key keyslot where the keyY is one of 6 keyYs loaded via the keyY index stored in the ticket. AES-CBC mode is used where the IV is the big-endian titleID. Note that on a retail unit index0 is a retail keyY, while on a dev-unit index0 is the dev common-key which is a normal-key.(On retail for these keyYs, the hardware key-scrambler is used) | ||