Nand/private/movable.sed: Difference between revisions

Revision as of 23:42, 27 March 2013 view source Yellows8 (talk \| contribs) Bureaucrats, Administrators 6,264 edits No edit summary ← Older edit		Revision as of 19:56, 28 March 2013 view source Yellows8 (talk \| contribs) Bureaucrats, Administrators 6,264 edits No edit summary Newer edit →
Line 29:		Line 29:
	Movable.sed always exists on retail, however if this file doesn't exist the system will fall-back to using a console-unique keyY already in [[PSPXI:GetLocalFriendCodeSeed\|memory]], with the last 8-bytes being loaded from the 8-bytes following that u64. It's unknown whether movable.sed exists on development units.		Movable.sed always exists on retail, however if this file doesn't exist the system will fall-back to using a console-unique keyY already in [[PSPXI:GetLocalFriendCodeSeed\|memory]], with the last 8-bytes being loaded from the 8-bytes following that u64. It's unknown whether movable.sed exists on development units.

	The keyY is hashed with SHA256, the first 0x10-bytes from the hash is used for ID0 in [[SD Filesystem\|sdmc/Nintendo 3DS/<ID0>/<ID1>]] and [[Flash Filesystem\|nand/data/<ID0>]]~~. The hashed data is the text output from snprintf using format string "%02x"~~.		The keyY is hashed with SHA256, the first 0x10-bytes from the hash is used for ID0 in [[SD Filesystem\|sdmc/Nintendo 3DS/<ID0>/<ID1>]] and [[Flash Filesystem\|nand/data/<ID0>]].