By entering this site you need to consent to the use of cookies and their functional use according to this privacy policy. Cookies help us to provide the functional services of the website. Kindly read the below message of use and consent to the use.
The following cookies are stored and shared when accessing this website:
- Internal cookies for the MediaWiki site. This is used for user authentication and article modifications.
- Third-party cookies from Google providing services for Google AdSense and Google Analytics
We will never use data collected outside of the above scope.
Nintendo leaked a keyY normal-key pair before 3ds was even released :P
Line 175:
Line 175:
| 32c3 3ds talk (December 27, 2015)
| 32c3 3ds talk (December 27, 2015)
| [[User:Yellows8|Yellows8]]
| [[User:Yellows8|Yellows8]]
+
|-
+
| Leak of normal-key matching a key-generator key
+
| During the 3DS' development (June/July 2010) Nintendo added support installing encrypted content ([[CIA]]). Common-key index1 was intended to be a [[AES|hardware generated key]]. However while they added code to generate the key in hardware, they forgot to remove the normal-key for index1 (used elsewhere, likely old debug code). Nintendo later removed the normal key sometime before the first non-prototype firmware release.
+
+
+
Knowing the keyY and the normal-key for common-key index1, the devkit key-generator algorithm can be deduced (see "Hardware" above). Additionally the remaining devkit common-keys can be generated once the common-key keyX is recovered.
+
+
Note the devkit key-generator was discovered to be the same as the retail key-generator.
+
| Deducing the keyX for keyslot 0x3D and hardware key-generator algorithm. Generate remaining devkit common-keys.
+
| pre-[[1.0.0-0|1.0.0-X]]
+
|
+
| Shortly after the key-generator was revealed to be flawed at the 32c3 3ds talk