6,263
edits
Changes
Jump to navigation
Jump to search
Line 42:
Line 42: − + Line 50:
Line 50: − |- − | Any − | Any − | style="background: green" | Yes − | 0x2C − | Original keyslot (always used unless NoCrypto flag is set in ncchflag[7])
→Encryption: ...
As of [[7.0.0-13|7.0.0-X]] the system supports a new encryption method for secure-crypto (when ncchflag[3] != 0). Where a second key is generated using the same keyY but with another [[AES|keyslot]]. The second key is used to crypt the [[RomFS]] and [[ExeFS]] files which don't have filenames "icon" or "banner" (i.e. ".code" and ".firm"). While everything else is crypted with the original key. Note the CTR used is the same for both keys. This makes titles "recognizable" but not "launchable" on systems which don't support this method or the keyslot used.
As of [[7.0.0-13|7.0.0-X]] the system supports a new encryption method for secure-crypto (when ncchflag[3] != 0). Where a second key is generated using the same keyY but with another [[AES|keyslot]]. The second key is used to crypt the [[RomFS]] and [[ExeFS]] files which don't have filenames "icon" or "banner" (i.e. ".code" and ".firm"). While everything else is crypted with the original key. Note the CTR used is the same for both keys. This makes titles "recognizable" but not "launchable" on systems which don't support this method or the keyslot used.
See below for the keyslots used in NCCH crypto. As of [[9.6.0-24|9.6.0-X]], Old3DS Process9 will *only* use keyslot 0x25 when ncchflag[3] is non-zero.
See below for the secondary keyslots used in NCCH crypto(as mentioned above). As of [[9.6.0-24|9.6.0-X]], Old3DS Process9 will *only* use secondary-keyslot 0x25 when ncchflag[3] is non-zero.
{| class="wikitable" border="1"
{| class="wikitable" border="1"
|-
|-
! [[AES#Keyslot|AES Keyslots]]
! [[AES#Keyslot|AES Keyslots]]
! Notes
! Notes
|-
|-
| 0x01
| 0x01