Sealedkey / pfsSKKey: Difference between revisions
Jump to navigation
Jump to search
CelesteBlue (talk | contribs) No edit summary |
CelesteBlue (talk | contribs) |
||
| Line 9: | Line 9: | ||
! Offset !! Size !! Description | ! Offset !! Size !! Description | ||
|- | |- | ||
| 0x0 || 0x8 || | | 0x0 || 0x8 || Magic "pfsSKKey" | ||
|- | |- | ||
| 0x8 || 0x4 || Type (always 2) | | 0x8 || 0x4 || Type (always 2) | ||
|- | |- | ||
| 0xC || 0x4 || | | 0xC || 0x4 || Padding / unk | ||
|- | |- | ||
| 0x10 || 0x10 || IV for encrypted key | | 0x10 || 0x10 || IV for encrypted key | ||
Revision as of 20:57, 26 April 2018
sealedkey file is located in sce_sys folder of savedata/trophies. It is not PFS encrypted.
It is used as a per savedata/trophy key in PFS encryption/decryption whilst gamedata/addcont uses klicensee.
File Structure
| Offset | Size | Description |
|---|---|---|
| 0x0 | 0x8 | Magic "pfsSKKey" |
| 0x8 | 0x4 | Type (always 2) |
| 0xC | 0x4 | Padding / unk |
| 0x10 | 0x10 | IV for encrypted key |
| 0x20 | 0x10 | Encrypted key |
| 0x30 | 0x20 | HMAC Value |
Decryption
The first step is to check the HMAC of the file. The process is to use the HMAC key from the Keys#PFS_Secret_Keys page to check the HMAC at position 0x30 in the file. If it is correct, it proceeds to use the pfsSKKey_EncKey to decrypt the value at +0x20 using the value at +0x10 as the IV.