SD title export - Revision history

Hiccup: Hiccup moved page Tad to SD title export

2024-04-06T19:23:48Z

Hiccup moved page Tad to SD title export

← Older revision	Revision as of 23:23, 6 April 2024
(No difference)

2024-04-06T19:23:27Z

no evidence these are TAD files - they don't match them at all

← Older revision		Revision as of 23:23, 6 April 2024
Line 1:		Line 1:
	The System Settings application delivered with each DSi can be used to export applications from NAND to SD. The bin files created on SD are using the ~~Tad~~ file structure. ~~Tad files~~ are encrypted with AES CCM (CTR with CBC-MAC), using a combination of a shared key and a console specific key.		The System Settings application delivered with each DSi can be used to export applications from NAND to SD. The bin files created on SD are using the following file structure. They are encrypted with AES CCM (CTR with CBC-MAC), using a combination of a shared key and a console specific key.

	The application itself (APP), and the title metadata (TMD) is encrypted with a console specific key. This means that Nintendo intended that these files can only be imported back into the same DSi.		The application itself (APP), and the title metadata (TMD) is encrypted with a console specific key. This means that Nintendo intended that these files can only be imported back into the same DSi.
Line 7:		Line 7:
	[[ES block encryption]] is used to encrypt the header block, footer block, and the 11 content parts. Each are their own seperate ES blocks.		[[ES block encryption]] is used to encrypt the header block, footer block, and the 11 content parts. Each are their own seperate ES blocks.

	= ~~Tad file~~ structure overview =		= File structure overview =

	{\| class="wikitable"		{\| class="wikitable"

2022-10-14T01:07:36Z

Header block @ 0x4020 (size 0xB4): HWINFO_N thing seems to be some kind of console ID because it's checked before import

2010-12-27T03:26:14Z

Tad file structure overview

← Older revision		Revision as of 06:26, 27 December 2010
Line 16:		Line 16:
	\|-		\|-
	\| 0x0		\| 0x0
	\| 0x4020 ?		\| 0x4020
	\| Banner/Icon		\| Banner/Icon
	\|-		\|-
	\| 0x4020		\| 0x4020
	\| ~~0xB4~~		\| 0xD4
	\| Header		\| Header
	\|-		\|-
Line 32:		Line 32:
	\|}		\|}

	The banner, header, footer and savegame are encrypted with a shared key between each DSi. The other content parts are encrypted with a console specific key.		The banner, header, footer and savegame are encrypted with a shared key between each DSi. The other content parts are encrypted with a console specific key.

	= Header block @ 0x4020 (size 0xB4) =		= Header block @ 0x4020 (size 0xB4) =

2010-10-20T00:20:04Z

@@ Line 5: / Line 5: @@
 While the banner, the public savegame, and several other metablocks are encrypted with a shared key, which means any DSi can inspect these parts of the file.
-[[ES block encryption]] is used to encrypt the header block, footer block, and the 11 parts. Each are their own seperate ES blocks.
+[[ES block encryption]] is used to encrypt the header block, footer block, and the 11 content parts. Each are their own seperate ES blocks.
-= header block @ 0x4020 (size 0xB4) =
+{| class="wikitable"
   0000000: 34 41 4e 54 31 30 00 01 74 e9 2c 1e 24 00 00 00  4ANT10..t.,.$...
   0000010: d6 e0 39 c3 98 3f 06 b6 9a b2 9d 14 e7 06 e9 00  ..9..?..........

2010-10-19T21:16:35Z

← Older revision		Revision as of 01:16, 20 October 2010
Line 1:		Line 1:
	The System Settings application delivered with each DSi can be used to export applications from NAND to SD. The files created on SD are encrypted with AES CCM (CTR with CBC-MAC), using a combination of a shared key and a console specific key.		The System Settings application delivered with each DSi can be used to export applications from NAND to SD. The bin files created on SD are using the Tad file structure. Tad files are encrypted with AES CCM (CTR with CBC-MAC), using a combination of a shared key and a console specific key.

	The application itself (APP), and the title metadata (TMD) is encrypted with a console specific key. This means that Nintendo intended that these files can only be imported back into the same DSi.		The application itself (APP), and the title metadata (TMD) is encrypted with a console specific key. This means that Nintendo intended that these files can only be imported back into the same DSi.

2010-10-19T21:15:54Z

moved Exporting Apps to Tad: I DO NOT NEED A REASON

← Older revision	Revision as of 01:15, 20 October 2010
(No difference)

2010-07-11T18:38:13Z

2010-07-06T02:48:22Z

footer block

2010-07-06T02:45:48Z

footer block

← Older revision		Revision as of 06:45, 6 July 2010
Line 154:		Line 154:
	\|-		\|-
	\| 0x00		\| 0x00
	\| 80		\| 20
	\| ~~Unknown~~		\| SHA1 of banner
	\|-		\|-
	\| ~~0x50~~		\| 0x14
	\| ~~150*2~~		\| 20
	\| ~~Producer Company (UCS-2)~~		\| SHA1 of tna4
	\|-		\|-
	\| ~~0xDC~~		\| 0x28
	\| 20		\| 20
	\| ~~SHA-1~~ of ~~(?)~~		\| SHA1 of tmd
	\|-		\|-
	\| ~~0x100~~		\| 0x3c
	\| ~~0x1c0~~		\| 20*8
	\| ECC signature (by ~~console)~~		\| SHA1 of up to 8 contents [if unused, can be whatever happened to be in memory before]
			\|-
			\| 0xdc
			\| 20
			\| SHA-1 of save data
			\|-
			\| 0xf0
			\| 20
			\| SHA-1 of ?
			\|-
			\| 0x104
			\| 0x3c
			\| ECC signature of previous 0x104 bytes with AP cert
			\|-
			\| 0x140
			\| 0x180
			\| AP cert, signed by TW cert
	\|-		\|-
	\| ~~0x2C0~~		\| 0x2c0
	\| 0x180		\| 0x180
	\| ~~Console signature~~ (see dev.kp)		\| TW cert, specific to a console (see dev.kp)
	\|}		\|}

	It is assumed that this block contains an ECC signature, aswell as the console id and serial of the DSi that exported the file, as part of a Nintendo cert. Much like the Wii, the DSi carries with it a private ECC key that it can use to sign things, and a certificate signed by Nintendo that attests to the fact that the public ECC key belongs to a genuine DSi.		It is assumed that this block contains an ECC signature, aswell as the console id and serial of the DSi that exported the file, as part of a Nintendo cert. Much like the Wii, the DSi carries with it a private ECC key that it can use to sign things, and a certificate signed by Nintendo that attests to the fact that the public ECC key belongs to a genuine DSi.