DSiWare Exports - Revision history

Jason0597 at 18:56, 8 September 2018

2018-09-08T16:56:32Z

← Older revision		Revision as of 20:56, 8 September 2018
Line 82:		Line 82:

	These hashes are the same hashes used for generating each section's MAC stored in the metadata block. X = 0x40 + totalcontentsections*0x20.		These hashes are the same hashes used for generating each section's MAC stored in the metadata block. X = 0x40 + totalcontentsections*0x20.

			The curve sect233r1 is used for all related ECDSA signing operations

	=File Structure v1=		=File Structure v1=

Yellows8: /* Footer */

2013-04-26T20:08:59Z

Footer

← Older revision		Revision as of 00:08, 27 April 2013
Line 66:		Line 66:
	\| 0x0 + X		\| 0x0 + X
	\| 0x3C		\| 0x3C
	\| ECDSA signature using ~~SHA256~~ over the previous hashes, signed by the APCert.		\| ECDSA signature using SHA-256 over the previous hashes, signed by the APCert.
	\|-		\|-
	\| 0x3C + X		\| 0x3C + X

Yellows8: /* Footer */

2013-04-26T20:07:53Z

Footer

← Older revision		Revision as of 00:07, 27 April 2013
Line 66:		Line 66:
	\| 0x0 + X		\| 0x0 + X
	\| 0x3C		\| 0x3C
	\| ECDSA signature over the previous hashes, signed by the APCert.		\| ECDSA signature using SHA256 over the previous hashes, signed by the APCert.
	\|-		\|-
	\| 0x3C + X		\| 0x3C + X

Yellows8 at 01:14, 26 April 2013

2013-04-25T23:14:03Z

← Older revision		Revision as of 03:14, 26 April 2013
Line 48:		Line 48:
	\| 0x10		\| 0x10
	\| 0x10		\| 0x10
	\| IV, generated by the RNG.		\| IV, generated by the [[PSPXI:GenerateRandomBytes\|RNG]].
	\|}		\|}

Line 70:		Line 70:
	\| 0x3C + X		\| 0x3C + X
	\| 0x180		\| 0x180
	\| ECDSA "APXXXXXXXXXXXXXXXX" cert signed by the below [[CTCert]], where X is random lowercase ASCII hex data.		\| ECDSA "APXXXXXXXXXXXXXXXX" cert signed by the below [[CTCert]], where X is [[PSPXI:GenerateRandomBytes\|random]] lowercase ASCII hex data.
	\|-		\|-
	\| 0x1BC + X		\| 0x1BC + X

Yellows8: /* DSiWare Export Types */

2013-04-25T19:02:56Z

DSiWare Export Types

← Older revision		Revision as of 23:02, 25 April 2013
Line 33:		Line 33:
	\|}		\|}

	For NATIVE_FIRM versions where this DSiWare export [[~~AMPXI~~:ExportDSiWare\|type]] field is unused, format version v1 is used with 4 content sections. Otherwise when this field is used, see the above table. [[System Settings]] uses type 1, regardless of the System Settings title-version.		For NATIVE_FIRM versions where this DSiWare export [[AM:ExportDSiWare\|type]] field is unused, format version v1 is used with 4 content sections. Otherwise when this field is used, see the above table. [[System Settings]] uses type 1 for [[AM:ExportDSiWare\|exporting]] DSiWare, regardless of the System Settings title-version.

	=Block Metadata=		=Block Metadata=

Yellows8: /* DSiWare Export Types */

2013-04-25T17:14:00Z

DSiWare Export Types

← Older revision		Revision as of 21:14, 25 April 2013
Line 14:		Line 14:
	\| 0-6		\| 0-6
	\|		\|
	\| ~~Invalid~~		\| Same as value 14.
	\|-		\|-
	\| 7-11		\| 7-11
Line 33:		Line 33:
	\|}		\|}

	For NATIVE_FIRM versions where this DSiWare export [[AMPXI:ExportDSiWare\|type]] field is unused, format version v1 is used with 4 content sections. Otherwise when this field is used, see the above table.		For NATIVE_FIRM versions where this DSiWare export [[AMPXI:ExportDSiWare\|type]] field is unused, format version v1 is used with 4 content sections. Otherwise when this field is used, see the above table. [[System Settings]] uses type 1, regardless of the System Settings title-version.

	=Block Metadata=		=Block Metadata=

Yellows8: /* Footer */

2013-04-25T15:02:54Z

Footer

← Older revision		Revision as of 19:02, 25 April 2013
Line 70:		Line 70:
	\| 0x3C + X		\| 0x3C + X
	\| 0x180		\| 0x180
	\| ECDSA "APXXXXXXXXXXXXXXXX" cert signed by the [[CTCert]], where X is random lowercase ASCII hex data.		\| ECDSA "APXXXXXXXXXXXXXXXX" cert signed by the below [[CTCert]], where X is random lowercase ASCII hex data.
	\|-		\|-
	\| 0x1BC + X		\| 0x1BC + X

Yellows8: /* Footer */

2013-04-25T01:01:38Z

Footer

← Older revision		Revision as of 05:01, 25 April 2013
Line 66:		Line 66:
	\| 0x0 + X		\| 0x0 + X
	\| 0x3C		\| 0x3C
	\| ECDSA signature over the previous ~~data~~, signed by the ~~AP cert?~~		\| ECDSA signature over the previous hashes, signed by the APCert.
	\|-		\|-
	\| 0x3C + X		\| 0x3C + X

Yellows8 at 23:23, 24 April 2013

2013-04-24T21:23:19Z

← Older revision		Revision as of 01:23, 25 April 2013
Line 1:		Line 1:
	The DSiWare exported from a 3DS is located at "[[SD_Filesystem\|sdmc]]:/Nintendo 3DS/<ID0>/<ID1>/Nintendo DSiWare". Filenames are same format as [http://dsibrew.org/wiki/Tad DSi]: "<TitleID-Low>.bin". The below sizes include the 0x20-byte block metadata.		The DSiWare exported from a 3DS is located at "[[SD_Filesystem\|sdmc]]:/Nintendo 3DS/<ID0>/<ID1>/Nintendo DSiWare". Filenames are same format as [http://dsibrew.org/wiki/Tad DSi]: "<TitleID-Low>.bin". The below sizes include the 0x20-byte block metadata.

	DSiWare exported from 3DS use [[Nand/private/movable.sed\|keyslots]] initialized by movable.sed. Each section is encrypted with AES-CBC.		DSiWare exported from 3DS use console-unique [[Nand/private/movable.sed\|keyslots]] initialized by movable.sed. Each section is encrypted with AES-CBC.

	The content sections are ordered the same way as DSi: TMD, SRL from content0, <content1-7 for format v2>, public.sav, and banner.sav when banner.sav exists. When the DSiWare export type is 7-11, the 12th content section is the private.sav, if it exists.(ContentX here is the .app data from TWL-NAND /title)		The content sections are ordered the same way as DSi: TMD, SRL from content0, <content1-7 for format v2>, public.sav, and banner.sav when banner.sav exists. When the DSiWare export type is 7-11, the 12th content section is the private.sav, if it exists.(ContentX here is the .app data from TWL-NAND /title)
Line 51:		Line 51:
	\|}		\|}

	Each section begins with the payload encrypted data, followed by this block metadata. The hash used for the MAC is calculated over ~~the~~ the cleartext payload~~, however it's unknown how this hash is calculated~~. This hash used for generating the MAC is also stored in the footer.		Each section begins with the payload encrypted data, followed by this block metadata. The SHA-256 hash used for the MAC is calculated over the cleartext payload. This hash used for generating the MAC is also stored in the footer.

	=Footer=		=Footer=

Yellows8 at 22:46, 24 April 2013

2013-04-24T20:46:40Z

← Older revision		Revision as of 00:46, 25 April 2013
Line 99:		Line 99:
	\|-		\|-
	\| 0x40E0		\| 0x40E0
	\| 0x340 + X, where X is the total size of the hashes stored in the footer.		\| 0x340 + 0x20 + X, where X is the total size of the hashes stored in the footer.
	\| Footer section		\| Footer section
	\|-		\|-
Line 175:		Line 175:
	\|-		\|-
	\| 0x4130		\| 0x4130
	\| 0x340 + X, where X is the total size of the hashes stored in the footer.		\| 0x340 + 0x20 + X, where X is the total size of the hashes stored in the footer.
	\| Footer section		\| Footer section
	\|-		\|-