Changes

Jump to navigation Jump to search
787 bytes added ,  06:26, 27 December 2010
m
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.
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.
 
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.
    +
= Tad file structure overview =
   −
= header =  
+
{| class="wikitable"
 +
|-
 +
! Offset
 +
! Size
 +
! Description
 +
|-
 +
| 0x0
 +
| 0x4020
 +
| Banner/Icon
 +
|-
 +
| 0x4020
 +
| 0xD4
 +
| Header
 +
|-
 +
| 0x40F4
 +
| 0x460
 +
| Footer (certificates/hashes)
 +
|-
 +
| 0x4554
 +
| -
 +
| Content parts in sequence (TMD, SRL, savegame, custom banner).
 +
|}
 +
 
 +
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) =  
 
  0000000: 34 41 4e 54 31 30 00 01 74 e9 2c 1e 24 00 00 00  4ANT10..t.,.$...
 
  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..?..........
 
  0000010: d6 e0 39 c3 98 3f 06 b6 9a b2 9d 14 e7 06 e9 00  ..9..?..........
Line 75: Line 101:  
|}
 
|}
   −
= footer block =
+
= footer block @ 0x40F4 (size 0x460) =
    
  0000000: d6 f3 24 7c a1 0f 4a dc cd 07 34 d6 ce 62 32 93  ..$|..J...4..b2.
 
  0000000: d6 f3 24 7c a1 0f 4a dc cd 07 34 d6 ce 62 32 93  ..$|..J...4..b2.
Line 154: Line 180:  
|-
 
|-
 
| 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
 +
| SHA1 of save data
 +
|-
 +
| 0xf0
 +
| 20
 +
| SHA1 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.

Navigation menu