NCCH: Difference between revisions
No edit summary |
|||
| Line 178: | Line 178: | ||
! INDEX | ! INDEX | ||
! DESCRIPTION | ! DESCRIPTION | ||
|- | |||
| 4 | |||
| Content Platform (1 = CTR) | |||
|- | |- | ||
| 5 | | 5 | ||
| | | Content Type Bit-masks: RomFS = 0x1, ExeFS = 0x2, SystemUpdate = 0x4, Manual = 0x8, Child = (0x4<nowiki>|</nowiki>0x8), Trial = 0x10. When 'RomFS' is set, but not 'ExeFS', NCCH is a CFA. Otherwise when 'ExeFS' is set, NCCH is a CXI. | ||
|- | |||
| 6 | |||
| Content Unit Size i.e. u32 ContentUnitSize = 0x200*2^flags[6]; | |||
|- | |||
| 7 | |||
| Bit-masks: FixedCryptoKey = 0x1, NoMountRomFs = 0x2, NoCrypto = 0x4 | |||
|} | |} | ||
CXIs NCCH header signature is verified using the RSA public key stored in the accessdesc,(which follows the exheader) while CFAs NCCH header is verified with a fixed RSA public key. | CXIs NCCH header signature is verified using the RSA public key stored in the accessdesc,(which follows the exheader) while CFAs NCCH header is verified with a fixed RSA public key. | ||