More actions
No edit summary |
No edit summary |
||
Line 2: | Line 2: | ||
|title=NDecrypt | |title=NDecrypt | ||
|image=NDecrypt.jpg | |image=NDecrypt.jpg | ||
|description=Cartridge encrypt/decrypt | |description=Cartridge encrypt/decrypt. | ||
|author=SabreTools | |author=SabreTools | ||
|lastupdated=2020/12/18 | |lastupdated=2020/12/18 | ||
Line 8: | Line 8: | ||
|version=0.2.2 | |version=0.2.2 | ||
|license=Mixed | |license=Mixed | ||
|download=https://dlhb.gamebrew.org/ | |download=https://dlhb.gamebrew.org/3dshomebrews/ndecrypt.7z | ||
|website=https://github.com/SabreTools/NDecrypt | |website=https://github.com/SabreTools/NDecrypt | ||
|source=https://github.com/SabreTools/NDecrypt | |source=https://github.com/SabreTools/NDecrypt | ||
}} | }} | ||
< | NDecrypt is a tool that allows you to encrypt and decrypt your personally dumped NDS and N3DS roms with minimal hassle. The only caveat right now is that you need a <code>keys.bin</code> file for your personally obtained encryption keys. | ||
This is a code port of 3 different programs: | This is a code port of 3 different programs: | ||
* <code>3ds_encrypt.py</code> | * <code>3ds_encrypt.py</code> | ||
* <code>3ds_decrypt.py</code> | * <code>3ds_decrypt.py</code> | ||
* <code>woodsec</code> (part of [https://github.com/TuxSH/wooddumper wooddumper]) | * <code>woodsec</code> (part of [https://github.com/TuxSH/wooddumper wooddumper]) | ||
== | ==User guide== | ||
===How to use=== | |||
'''Note:''' This overwrites the input files, so make backups if you're working on your original, personal dumps. | |||
NDecrypt.exe <operation> [flags] <path> ... | |||
Possible values for <operation>: | |||
e, encrypt - Encrypt the input files | |||
d, decrypt - Decrypt the input files | |||
Possible values for [flags] (one or more can be used): | |||
-c, --citra - Enable using aes_keys.txt instead of keys.bin | |||
-dev, --development - Enable using development keys, if available | |||
-f, --force - Force operation by avoiding sanity checks | |||
-h, --hash - Output size and hashes to a companion file | |||
-k, --keyfile <path> - Path to keys.bin or aes_keys.txt | |||
<path> can be any file or folder that contains uncompressed items. | |||
More than one path can be specified at a time. | |||
Mixed folders or inputs are also accepted, you can decrypt or encrypt multiple files, regardless of their type. | |||
This being said, you can only do encrypt or decrypt at one time. | |||
== | ===keys.bin=== | ||
This is used only for Nintendo 3DS and New 3DS files. You need the 9 16-bit keys in little endian format (most common extraction methods produce big endian, so keep that in mind). | |||
It's recommended that you fill with 0x00 if you don't have access to a particular value so it doesn't mess up the read. They need to be in the following order: | |||
* Hardware constant | * Hardware constant | ||
Line 58: | Line 58: | ||
* DevKeyX0x2C | * DevKeyX0x2C | ||
The last 4 are only required if you use the <code>-dev</code> flag. Once again, don't ask for these, please. If you're missing a required key, then things won't work | The last 4 are only required if you use the <code>-dev</code> flag. Once again, don't ask for these, please. If you're missing a required key, then things won't work. | ||
== | ===Compatibility rates=== | ||
Here's a list of the supported sets and their current compatibility percentages with woodsec and the Python scripts (as of 2020-12-19): | |||
* Nintendo DS - >99% compatible (Both encryption and decryption). | |||
* Nintendo DSi - 100% compatible (Both encryption and decryption). | |||
* Nintendo 3DS - 100% compatible (Both encryption and decryption). | |||
* Nintendo New 3DS - 100% compatible (Both encryption and decryption). | |||
Please note the above numbers are based on the current, documented values. | |||
The notable exceptions to this tend to be unlicensed carts which may be dumped incorrectly or have odd information stored in their secure area. | |||
== | ==Credits== | ||
Thanks to the developers of the original programs for doing the actual hard work to figure things out. | |||
Also thanks to everyone who helped to test this against the original programs and made code suggestions. | |||
Disclaimer: This program is only for use with personally dumped files and keys and is not meant for enabling illegal activity. | |||
== | ==External links== | ||
* GitHub - https://github.com/SabreTools/NDecrypt | |||
[[Category:3DS homebrew applications]] | |||
[[Category:PC utilities for 3DS homebrew]] |
Revision as of 02:35, 19 March 2022
NDecrypt | |
---|---|
File:NDecrypt.jpg | |
General | |
Author | SabreTools |
Type | PC Utilities |
Version | 0.2.2 |
License | Mixed |
Last Updated | 2020/12/18 |
Links | |
Download | |
Website | |
Source | |
NDecrypt is a tool that allows you to encrypt and decrypt your personally dumped NDS and N3DS roms with minimal hassle. The only caveat right now is that you need a keys.bin
file for your personally obtained encryption keys.
This is a code port of 3 different programs:
3ds_encrypt.py
3ds_decrypt.py
woodsec
(part of wooddumper)
User guide
How to use
Note: This overwrites the input files, so make backups if you're working on your original, personal dumps.
NDecrypt.exe <operation> [flags] <path> ... Possible values for <operation>: e, encrypt - Encrypt the input files d, decrypt - Decrypt the input files Possible values for [flags] (one or more can be used): -c, --citra - Enable using aes_keys.txt instead of keys.bin -dev, --development - Enable using development keys, if available -f, --force - Force operation by avoiding sanity checks -h, --hash - Output size and hashes to a companion file -k, --keyfile <path> - Path to keys.bin or aes_keys.txt <path> can be any file or folder that contains uncompressed items. More than one path can be specified at a time.
Mixed folders or inputs are also accepted, you can decrypt or encrypt multiple files, regardless of their type.
This being said, you can only do encrypt or decrypt at one time.
keys.bin
This is used only for Nintendo 3DS and New 3DS files. You need the 9 16-bit keys in little endian format (most common extraction methods produce big endian, so keep that in mind).
It's recommended that you fill with 0x00 if you don't have access to a particular value so it doesn't mess up the read. They need to be in the following order:
- Hardware constant
- KeyX0x18
- KeyX0x1B
- KeyX0x25
- KeyX0x2C
- DevKeyX0x18
- DevKeyX0x1B
- DevKeyX0x25
- DevKeyX0x2C
The last 4 are only required if you use the -dev
flag. Once again, don't ask for these, please. If you're missing a required key, then things won't work.
Compatibility rates
Here's a list of the supported sets and their current compatibility percentages with woodsec and the Python scripts (as of 2020-12-19):
- Nintendo DS - >99% compatible (Both encryption and decryption).
- Nintendo DSi - 100% compatible (Both encryption and decryption).
- Nintendo 3DS - 100% compatible (Both encryption and decryption).
- Nintendo New 3DS - 100% compatible (Both encryption and decryption).
Please note the above numbers are based on the current, documented values.
The notable exceptions to this tend to be unlicensed carts which may be dumped incorrectly or have odd information stored in their secure area.
Credits
Thanks to the developers of the original programs for doing the actual hard work to figure things out.
Also thanks to everyone who helped to test this against the original programs and made code suggestions.
Disclaimer: This program is only for use with personally dumped files and keys and is not meant for enabling illegal activity.