Title metadata - Revision history

Pk11: Improve formatting

2022-12-20T03:28:07Z

Improve formatting

← Older revision		Revision as of 06:28, 20 December 2022
Line 1:		Line 1:
	'''Title metadata''', or '''TMD''' for short, is a format used to store information about a title (DSiWare, etc.) and all its installed contents, including which contents they consist of and their ~~SHA1~~ hashes. The format between Wii and DSi Title metadata ''appears'' to be identical; this includes endianness, so byteswaps are often needed on the DSi.		'''Title metadata''', or '''TMD''' for short, is a format used to store information about a title ([[DSiWare]], etc.) and all its installed contents, including which contents they consist of and their {{Wikipedia\|SHA-1}} hashes. The format between Wii and DSi Title metadata ''appears'' to be identical; this includes {{Wikipedia\|endianness}}, so byteswaps are often needed on the DSi.

	Many operations are done in terms of 64-byte blocks, which means you will often see padding out to the nearest 64-byte boundary at the end of a field.		Many operations are done in terms of 64-byte blocks, which means you will often see padding out to the nearest 64-byte boundary at the end of a field.

	Example of a Nintendo DSi TMD : http://nus.cdn.t.shop.nintendowifi.net/ccs/download/0003000f484e4c4a/tmd ("HNLJ", or Japanese [[Version Data]].)		Example of a Nintendo DSi TMD: http://nus.cdn.t.shop.nintendowifi.net/ccs/download/0003000f484e4c4a/tmd ("HNLJ", or Japanese [[Version Data]].)

	The certificate chain at the end of the file seems to always/usually have a size in bytes of ~~1792~~ and a ~~SHA256~~ of 03CE2468F00D1AAEA52D7193A2312B0FE87ECE72D43381C3B6BD4C57E700CDD7.		The certificate chain at the end of the file seems to always/usually have a size in bytes of 1,792 and a {{Wikipedia\|SHA-256}} of <code>03CE2468F00D1AAEA52D7193A2312B0FE87ECE72D43381C3B6BD4C57E700CDD7</code>.

	== Structure ==		== Structure ==

Hallowizer: /* Header */ fixed a typo

2022-10-13T22:58:44Z

Header: fixed a typo

← Older revision		Revision as of 02:58, 14 October 2022
Line 47:		Line 47:
	\| 0x183		\| 0x183
	\| 1		\| 1
	\| Padding modulo 64		\| Padding modulo 4
	\|-		\|-
	\| 0x184		\| 0x184

Hallowizer: byteswaps seem to exist because DSi is little endian

2022-06-28T20:29:47Z

byteswaps seem to exist because DSi is little endian

← Older revision		Revision as of 00:29, 29 June 2022
Line 1:		Line 1:
	'''Title metadata''', or '''TMD''' for short, is a format used to store information about a title (DSiWare, etc.) and all its installed contents, including which contents they consist of and their SHA1 hashes. The format between Wii and DSi Title metadata ''appears'' to be identical.		'''Title metadata''', or '''TMD''' for short, is a format used to store information about a title (DSiWare, etc.) and all its installed contents, including which contents they consist of and their SHA1 hashes. The format between Wii and DSi Title metadata ''appears'' to be identical; this includes endianness, so byteswaps are often needed on the DSi.

	Many operations are done in terms of 64-byte blocks, which means you will often see padding out to the nearest 64-byte boundary at the end of a field.		Many operations are done in terms of 64-byte blocks, which means you will often see padding out to the nearest 64-byte boundary at the end of a field.

Hallowizer: /* Header */ system version is probably always 0

2021-11-10T02:35:17Z

Header: system version is probably always 0

← Older revision		Revision as of 05:35, 10 November 2021
Line 51:		Line 51:
	\| 0x184		\| 0x184
	\| 8		\| 8
	\| System Version		\| System Version; probably always 0
	\|-		\|-
	\| 0x18C		\| 0x18C

Hiccup at 18:14, 18 June 2021

2021-06-18T16:14:44Z

← Older revision		Revision as of 20:14, 18 June 2021
Line 5:		Line 5:
	Example of a Nintendo DSi TMD : http://nus.cdn.t.shop.nintendowifi.net/ccs/download/0003000f484e4c4a/tmd ("HNLJ", or Japanese [[Version Data]].)		Example of a Nintendo DSi TMD : http://nus.cdn.t.shop.nintendowifi.net/ccs/download/0003000f484e4c4a/tmd ("HNLJ", or Japanese [[Version Data]].)

	The certificate chain at the end of the file seems to always/usually have a SHA256 of 03CE2468F00D1AAEA52D7193A2312B0FE87ECE72D43381C3B6BD4C57E700CDD7.		The certificate chain at the end of the file seems to always/usually have a size in bytes of 1792 and a SHA256 of 03CE2468F00D1AAEA52D7193A2312B0FE87ECE72D43381C3B6BD4C57E700CDD7.

	== Structure ==		== Structure ==

Hiccup at 16:54, 18 June 2021

2021-06-18T14:54:04Z

← Older revision		Revision as of 18:54, 18 June 2021
Line 5:		Line 5:
	Example of a Nintendo DSi TMD : http://nus.cdn.t.shop.nintendowifi.net/ccs/download/0003000f484e4c4a/tmd ("HNLJ", or Japanese [[Version Data]].)		Example of a Nintendo DSi TMD : http://nus.cdn.t.shop.nintendowifi.net/ccs/download/0003000f484e4c4a/tmd ("HNLJ", or Japanese [[Version Data]].)

	The certificate chain at the end of the file seems to always/usually have a SHA256 of 03CE2468F00D1AAEA52D7193A2312B0FE87ECE72D43381C3B6BD4C57E700CDD7/		The certificate chain at the end of the file seems to always/usually have a SHA256 of 03CE2468F00D1AAEA52D7193A2312B0FE87ECE72D43381C3B6BD4C57E700CDD7.

	== Structure ==		== Structure ==

Hiccup at 16:52, 18 June 2021

2021-06-18T14:52:36Z

← Older revision		Revision as of 18:52, 18 June 2021
Line 4:		Line 4:

	Example of a Nintendo DSi TMD : http://nus.cdn.t.shop.nintendowifi.net/ccs/download/0003000f484e4c4a/tmd ("HNLJ", or Japanese [[Version Data]].)		Example of a Nintendo DSi TMD : http://nus.cdn.t.shop.nintendowifi.net/ccs/download/0003000f484e4c4a/tmd ("HNLJ", or Japanese [[Version Data]].)

			The certificate chain at the end of the file seems to always/usually have a SHA256 of 03CE2468F00D1AAEA52D7193A2312B0FE87ECE72D43381C3B6BD4C57E700CDD7/

	== Structure ==		== Structure ==

TwelveBaud: Added what title the example TMD is for.

2010-01-28T00:58:14Z

Added what title the example TMD is for.

← Older revision		Revision as of 03:58, 28 January 2010
Line 3:		Line 3:
	Many operations are done in terms of 64-byte blocks, which means you will often see padding out to the nearest 64-byte boundary at the end of a field.		Many operations are done in terms of 64-byte blocks, which means you will often see padding out to the nearest 64-byte boundary at the end of a field.

	Example of a Nintendo DSi TMD : http://nus.cdn.t.shop.nintendowifi.net/ccs/download/0003000f484e4c4a/tmd		Example of a Nintendo DSi TMD : http://nus.cdn.t.shop.nintendowifi.net/ccs/download/0003000f484e4c4a/tmd ("HNLJ", or Japanese [[Version Data]].)

	== Structure ==		== Structure ==

CashMan at 11:18, 10 April 2009

2009-04-10T09:18:15Z

← Older revision		Revision as of 13:18, 10 April 2009
Line 2:		Line 2:

	Many operations are done in terms of 64-byte blocks, which means you will often see padding out to the nearest 64-byte boundary at the end of a field.		Many operations are done in terms of 64-byte blocks, which means you will often see padding out to the nearest 64-byte boundary at the end of a field.

			Example of a Nintendo DSi TMD : http://nus.cdn.t.shop.nintendowifi.net/ccs/download/0003000f484e4c4a/tmd

	== Structure ==		== Structure ==

	=== Header ===		=== Header ===

	{\| class="wikitable"		{\| class="wikitable"
	\|- style="background-color: #ddd;"		\|- style="background-color: #ddd;"

Blooper4912 at 18:37, 5 April 2009

2009-04-05T16:37:30Z

← Older revision		Revision as of 20:37, 5 April 2009
Line 1:		Line 1:
	'''Title metadata''' is a format used to store information about a title (DSiWare, etc.) and all its installed contents, including which contents they consist of and their SHA1 hashes. The format between Wii and DSi Title metadata ''appears'' to be identical.		'''Title metadata''', or '''TMD''' for short, is a format used to store information about a title (DSiWare, etc.) and all its installed contents, including which contents they consist of and their SHA1 hashes. The format between Wii and DSi Title metadata ''appears'' to be identical.

	Many operations are done in terms of 64-byte blocks, which means you will often see padding out to the nearest 64-byte boundary at the end of a field.		Many operations are done in terms of 64-byte blocks, which means you will often see padding out to the nearest 64-byte boundary at the end of a field.