Difference between revisions of "Flipbook XOR Pad"

From DSiBrew
Jump to navigation Jump to search
m (Removing unnecessary F-Bomb)
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Since the encryption used is AES-128-CTR, there's a static XOR pad (generated from the key) applied when encrypting/decrypting.
+
There's a static XOR pad applied when encrypting/decrypting files. (This pad *might* be generated using aes-ctr) It repeats each 0x40 (what a screw-up, Nintendo).
 
Here's the XOR pad used for the *.lst file (hexadecimal):
 
Here's the XOR pad used for the *.lst file (hexadecimal):
  
   00: XX XX XX XX XX XX A6 37 6E 11 38 CF A0 DD 85 C0
+
   00: F7 4C 6A 3A FB 82 A6 37 6E 11 38 CF A0 DD 85 C0
   10: C7 9B C4 D8 DD 28 8A 87 53 20 EE E0 0B BE B4 3A
+
   10: C7 9B C4 D8 DD 28 8A 87 53 20 EE E0 0B EB 43 A0
   20: 0D B5 5F 75 36 37 EB 35 6A 34 7F B5 0F 99 F7 EF
+
   20: DB 55 0F 75 36 37 EB 35 6A 34 7F B5 0F 99 F7 EF
   30: 43 25 CE A0 29 46 D9 D4 4D BB XX XX XX XX XX XX
+
   30: 43 25 CE A0 29 46 D9 D4 4D BB 04 66 68 08 F1 F8
  40: F7 4C 6A 3A FB 82 A6 37 6E 11 38 CF A0 DD 85 C0
 
  50: C7 9B C4 D8 DD 28 8A XX XX XX XX XX XX EB 43 A0
 
  60: DB 55 0F 75 36 37 EB 35 6A 34 7F B5 0F 99 F7 EF
 
  70: 43 25 CE A0 XX XX XX
 

Latest revision as of 15:38, 16 August 2009

There's a static XOR pad applied when encrypting/decrypting files. (This pad *might* be generated using aes-ctr) It repeats each 0x40 (what a screw-up, Nintendo). Here's the XOR pad used for the *.lst file (hexadecimal):

 00: F7 4C 6A 3A FB 82 A6 37 6E 11 38 CF A0 DD 85 C0
 10: C7 9B C4 D8 DD 28 8A 87 53 20 EE E0 0B EB 43 A0
 20: DB 55 0F 75 36 37 EB 35 6A 34 7F B5 0F 99 F7 EF
 30: 43 25 CE A0 29 46 D9 D4 4D BB 04 66 68 08 F1 F8