Titles: Difference between revisions
→Data Structure: add more cmd format details |
→Data Structure: add note about twlnand cmd files |
||
Line 281: | Line 281: | ||
For SD contents, each AES-CMAC is generated by combining the NCCH header without the signature (0x100-0x1FF), the Content Index and Content ID at the end, both as u32. Then calculate the SHA256 of the data and generate the AES-CMAC using the [[AES Registers#Keyslots|SD/NAND AES-CMAC key]]. | For SD contents, each AES-CMAC is generated by combining the NCCH header without the signature (0x100-0x1FF), the Content Index and Content ID at the end, both as u32. Then calculate the SHA256 of the data and generate the AES-CMAC using the [[AES Registers#Keyslots|SD/NAND AES-CMAC key]]. | ||
For TWLNAND contents, the process is currently unknown. | For TWLNAND contents, the process is currently unknown, but it appears to use a different keyslot(cmd file was identical even after a system format). | ||