DISA and DIFF: Difference between revisions
m →Partition table & partition descriptor: The padding doesn't actually belongs to the descriptor, according to the descriptor size in the header |
Correct CMAC for cart save |
||
| Line 17: | Line 17: | ||
| Gamecard | | Gamecard | ||
| DISA | | DISA | ||
| [[#CTR- | | [[#CTR-NOR0|CTR-NOR0]] | ||
| 0x19 | | 0x19 / 0x33 | ||
|- | |- | ||
| [[Savegames]] | | [[Savegames]] | ||
| Line 87: | Line 87: | ||
The data being authenticated by the AES CMAC is a 0x20-byte SHA-256 hash of a data block. The data block has different content formats among CMAC types. All types of data block contain a copy or a hash of the header, which is the start of the the rest of the verification chain, so the AES CMAC effectively authenticates the whole save image. Each type of data block is explained below. | The data being authenticated by the AES CMAC is a 0x20-byte SHA-256 hash of a data block. The data block has different content formats among CMAC types. All types of data block contain a copy or a hash of the header, which is the start of the the rest of the verification chain, so the AES CMAC effectively authenticates the whole save image. Each type of data block is explained below. | ||
=== CTR- | === CTR-NOR0 === | ||
This CMAC type is used for gamecard savegames. It is 0x28-byte long. | This CMAC type is used for gamecard savegames. It is 0x28-byte long. | ||
| Line 98: | Line 98: | ||
| 0x00 | | 0x00 | ||
| 8 | | 8 | ||
| Magic "CTR- | | Magic "CTR-NOR0" | ||
|- | |- | ||
| 0x8 | | 0x8 | ||
| Line 113: | Line 113: | ||
| 0x00 | | 0x00 | ||
| 8 | | 8 | ||
| Magic "CTR- | | Magic "CTR-SAV0" | ||
|- | |- | ||
| 0x08 | | 0x08 | ||