NCCH: Difference between revisions
m →CFA: Fixing links |
|||
Line 37: | Line 37: | ||
The extended header, the [[ExeFS]] and the [[RomFS]] are encrypted using 128-bit AES CTR. | The extended header, the [[ExeFS]] and the [[RomFS]] are encrypted using 128-bit AES CTR. | ||
By default encrypted regions are compressed with an LZ77 variant, then encrypted. The spec allows for both unencrypted and uncompressed regions to exist | By default encrypted regions are compressed with an LZ77 variant, then encrypted. The spec allows for both unencrypted and uncompressed regions to exist. Development units use a fixed system key for system titles. On retail part of the input [[AES]] engine key is unique per NCCH, the AES engine internally generates the final-normal key. | ||
On retail for SD applications, exheader_systeminfoflags.flag bit1 must be set. | |||
Retail CFAs use NCCH product code "CTR-P-CTAP", while retail title/gamecard CXIs use NCCH product code "CTR-P-XXXX". This product code is the NCCH [[Serials|serial code]]. The region-locking info checked by home menu is stored in the [[SMDH#BNR Region|icon]]. | Retail CFAs use NCCH product code "CTR-P-CTAP", while retail title/gamecard CXIs use NCCH product code "CTR-P-XXXX". This product code is the NCCH [[Serials|serial code]]. The region-locking info checked by home menu is stored in the [[SMDH#BNR Region|icon]]. |