Hacking Decrypt and Re-Encrypt NAND?

[drfsupercenter]

i guess your missing the point....to get the unique per device encryption...the device would need to be hacked, if its hacked, whats the point?
you cant just make a nand work from one console one a updated console without having the target console hacked too so you can re-encrypt the "donor nand" using that 3ds's unique encryption

When you decrypt the NAND, where is it getting the xorpad keys from? I thought the .bin file was generated on your computer...

 

[gamesquest1]

When you decrypt the NAND, where is it getting the xorpad keys from? I thought the .bin file was generated on your computer...

no you generate the xorpad on the console the nand is dumped from....so that xorpad is only any use to that specific 3ds's nand.

 

[drfsupercenter]

no you generate the xorpad on the console the nand is dumped from....so that xorpad is only any use to that specific 3ds's nand.

Oh, I see. So the reason you can decrypt a ROM with any 3DS is because they're all signed using the same common key, but we don't know what that is yet for NANDs?

 

[gamesquest1]

Oh, I see. So the reason you can decrypt a ROM with any 3DS is because they're all signed using the same common key, but we don't know what that is yet for NANDs?

every 3ds has its own unique key.......3ds roms need to be readable by all 3ds consoles.....the nand doesn't, so per device encryption basically kills off any hack one console and you hack them all situation

 

[justinkb]

We can already decrypt and (I believe) re-encrypt NAND partitions. The main issue is that there are some other console-specific bits in the firmware. Nintendo's System Transfer app itself literally copies stuff off the NAND to the other person's 3DS and then re-encrypts it under the new console's keys.

I think you're missing the point. This is all done via hardware operations on the 3DSes involved.