Nand/private/movable.sed: Difference between revisions

Line 22:

| 0x110

| 0x10

| [[AES]] engine keyY for 3 keyslots

| [[AES]] engine keyY for 3 keyslots (High u64 is a counter which is unsigned)

|}

This file is transferred to the destination 3DS during a [[System Transfer]]. The keyY high u64 loaded from movable.sed, is a counter which is incremented on the source 3DS during a [[System Transfer]]. This keyY is the console-unique portion of ~~these~~ 3 keyslots~~. All of the data~~ under [[SD Filesystem|sdmc/Nintendo 3DS/<ID0>/<ID1>]] and [[Flash Filesystem|nand/data/<ID0>]] ~~use these console-unique keyslots~~.

This keyY is the console-unique portion of the 3 keyslots used for everything stored under [[SD Filesystem|sdmc/Nintendo 3DS/<ID0>/<ID1>]] and [[Flash Filesystem|nand/data/<ID0>]]. This file is transferred to the destination 3DS during a [[System Transfer]]. This movable.sed counter is [[FS:InitializeCtrFileSystem|updated]] on the source 3DS during a [[System Transfer]], and when doing a system format with [[System Settings]].

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. ~~Therefore,~~ movable.sed ~~presumably doesn't exist~~ 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>]].

@@ Line 22: / Line 22: @@
 | 0x110
 | 0x10
-| [[AES]] engine keyY for 3 keyslots
+| [[AES]] engine keyY for 3 keyslots (High u64 is a counter which is unsigned)
 |}
-This file is transferred to the destination 3DS during a [[System Transfer]]. The keyY high u64 loaded from movable.sed, is a counter which is incremented on the source 3DS during a [[System Transfer]]. This keyY is the console-unique portion of these 3 keyslots. All of the data under [[SD Filesystem|sdmc/Nintendo 3DS/<ID0>/<ID1>]] and [[Flash Filesystem|nand/data/<ID0>]] use these console-unique keyslots.
+This keyY is the console-unique portion of the 3 keyslots used for everything stored under [[SD Filesystem|sdmc/Nintendo 3DS/<ID0>/<ID1>]] and [[Flash Filesystem|nand/data/<ID0>]]. This file is transferred to the destination 3DS during a [[System Transfer]]. This movable.sed counter is [[FS:InitializeCtrFileSystem|updated]] on the source 3DS during a [[System Transfer]], and when doing a system format with [[System Settings]].
-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. Therefore, movable.sed presumably doesn't exist 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>]].