NDecrypt 3DS: Difference between revisions

From GameBrew
(Created page with "{{Infobox 3DS homebrew | title = NDecrypt | image = https://dlhb.gamebrew.org/3dshomebrew/NDecrypt.jpg|250px | type = PC Utilities | version = v0.2.2 | licence = Mixed | autho...")
 
m (Text replacement - "Category:PC utilities for 3DS homebrew" to "")
 
(23 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Infobox 3DS homebrew
{{Infobox 3DS Homebrews
| title = NDecrypt
|title=NDecrypt
| image = https://dlhb.gamebrew.org/3dshomebrew/NDecrypt.jpg|250px
|image=Ndecrypt2.png
| type = PC Utilities
|description=Cartridge encrypt/decrypt.
| version = v0.2.2
|author=SabreTools
| licence = Mixed
|lastupdated=2023/01/07
| author = SabreTools
|type=File Operation
| website = https://github.com/SabreTools/NDecrypt
|version=0.2.5
| download = https://dlhb.gamebrew.org/3dshomebrew/NDecrypt.rar
|license=MIT
| source = https://dlhb.gamebrew.org/3dshomebrew/NDecrypt.rar
|download=https://dlhb.gamebrew.org/3dshomebrews/ndecrypt.7z
|website=https://github.com/SabreTools/NDecrypt
|source=https://github.com/SabreTools/NDecrypt
}}
}}
<youtube>iL5R83zxXpU</youtube>
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.


= NDecrypt =
This is a code port of 3 different programs: 3ds_encrypt.py, 3ds_decrypt.py and woodsec (part of [https://github.com/TuxSH/wooddumper wooddumper]).


A simple tool for simple people.
==User guide==
===How to use===
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.


== What is this? ==
Mixed folders or inputs are also accepted, you can decrypt or encrypt multiple files, regardless of their type.
 
This is a code port of 3 different programs:
 
* <code>3ds_encrypt.py</code>
* <code>3ds_decrypt.py</code>
* <code>woodsec</code> (part of [https://github.com/TuxSH/wooddumper wooddumper])
 
== No really, what is this? ==
 
This tool 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.
 
== So how do I use this? ==
 
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): -dev, --development - Enable using development keys, if available -f, --force - Force operation by avoiding sanity checks
 
<path> can be any file or folder that contains uncompressed items. More than one path can be specified at a time.


'''Note:''' This overwrites the input files, so make backups if you're working on your original, personal dumps.
'''Note:''' This overwrites the input files, so make backups if you're working on your original, personal dumps.


'''Note:''' 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. Without getting into the codes, you need the 9 16-bit keys in little endian format (most common extraction methods produce big endian, so keep that in mind).  
== I feel like something is missing... ==


You are! In fact, you may be asking, &quot;Hey, what was that <code>keys.bin</code> you mentioned??&quot;. I'm glad you asked. It's used only for Nintendo 3DS and New 3DS files. Since some people don't like reading code, 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:
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 56: Line 53:
* 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. Don't blame me, blame society. Or something. And yes, I'll fix this being required across the board at some point.
The last 4 are only required if you use the <code>-dev</code> flag. Once again, don't ask for these. 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.


== But does it work? ==
==Changelog==
'''v0.2.5'''
* License has been correctly set to MIT instead of the "whatever" mentioned before.
* Build targets for Windows x86, Windows x64, Linux x64, and OSX x64 have been added for packaging.
* .NET Core 3.1 has been removed as a build version.
* AppVeyor has been enabled to allow for easier testing of WIP builds.


As much as I'd like to think that this program is entirely without flaws, numbers need to speak for themselves sometimes. Here's a list of the supported sets and their current compatibility percentages with woodsec and the Python scripts (as of 2020-12-19):
'''v0.2.4'''
* .NET 5 support has been dropped.
* .NET 6 support (hashing and encrypt/decrypt) have been fixed.
* Internal structure changed to be more library-oriented.


* '''Nintendo DS''' - &gt;99% compatible (Both encryption and decryption)
'''v0.2.3'''
* '''Nintendo DSi''' - 100% compatible (Both encryption and decryption)
* Add support for outputting file hashes to a companion file.
* '''Nintendo 3DS''' - 100% compatible (Both encryption and decryption)
* Add support for alternate keyfile paths.
* '''Nintendo New 3DS''' - 100% compatible (Both encryption and decryption)
* Add support for Citra aes_keys.txt.
* Major internal cleanups and code separation.
* Converted core library to .NET Standard 2.0.
* Added .NET 6.0 as build target for main executable.


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.
'''v0.2.2'''
* Added a couple of fixes for NDS Prince of Persia carts that have mastering oddities.
* Added the .ids iQue DS extension to matching.
* Fixed the matching criteria for some of the NDS signatures.
* Added more improperly decrypted empty secure area NDS signatures.
* Remove forced pause at end of program run.
* Make keys.bin only required for 3DS and New 3DS processing.
* Add some try/catch blocks around processing so it doesn't hard crash (issue with incorrectly-named BIOS files).


== Anything else? ==
'''v0.2.1'''
* Merged two projects into one again, based on the Core version from last time. No changes to supported frameworks due to this.
* Reorganized a bit of the code internally in case other cart types get supported in the future.
* Added a couple of fixes for NDS Dragon Quest V carts that have mastering oddities.


I'd like to thank the developers of the original programs for doing the actual hard work to figure things out. I'd also like to thank everyone who helped to test this against the original programs and made code suggestions.
'''v0.2.0'''
* Internal cleanup of most of the code.
* Removed .NET Framework 4.6.1 build.
* Added .NET Framework 4.8, .NET Core 3.1, and .NET 5.0 builds.
* Fixed NDS secure areas.
* Fixed larger game carts.
* Fixed encrypting N3DS carts.
* Add force flags for NDS and N3DS.


Unofficially, this is entirely, 100% FOSS, no strings attached. I keep forgetting what license that is.
==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 ==
Disclaimer: This program is only for use with personally dumped files and keys and is not meant for enabling illegal activity.


This program is '''ONLY''' for use with personally dumped files and keys and is not meant for enabling illegal activity. I do not condone using this program for anything other than personal use and research. If this program is used for anything other than that, I cannot be held liable for anything that happens.
==External links==
* GitHub - https://github.com/SabreTools/NDecrypt

Latest revision as of 04:27, 6 May 2024

NDecrypt
Ndecrypt2.png
General
AuthorSabreTools
TypeFile Operation
Version0.2.5
LicenseMIT License
Last Updated2023/01/07
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 and woodsec (part of wooddumper).

User guide

How to use

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.

Note: This overwrites the input files, so make backups if you're working on your original, personal dumps.

keys.bin

This is used only for Nintendo 3DS and New 3DS files. Without getting into the codes, 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. 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.

Changelog

v0.2.5

  • License has been correctly set to MIT instead of the "whatever" mentioned before.
  • Build targets for Windows x86, Windows x64, Linux x64, and OSX x64 have been added for packaging.
  • .NET Core 3.1 has been removed as a build version.
  • AppVeyor has been enabled to allow for easier testing of WIP builds.

v0.2.4

  • .NET 5 support has been dropped.
  • .NET 6 support (hashing and encrypt/decrypt) have been fixed.
  • Internal structure changed to be more library-oriented.

v0.2.3

  • Add support for outputting file hashes to a companion file.
  • Add support for alternate keyfile paths.
  • Add support for Citra aes_keys.txt.
  • Major internal cleanups and code separation.
  • Converted core library to .NET Standard 2.0.
  • Added .NET 6.0 as build target for main executable.

v0.2.2

  • Added a couple of fixes for NDS Prince of Persia carts that have mastering oddities.
  • Added the .ids iQue DS extension to matching.
  • Fixed the matching criteria for some of the NDS signatures.
  • Added more improperly decrypted empty secure area NDS signatures.
  • Remove forced pause at end of program run.
  • Make keys.bin only required for 3DS and New 3DS processing.
  • Add some try/catch blocks around processing so it doesn't hard crash (issue with incorrectly-named BIOS files).

v0.2.1

  • Merged two projects into one again, based on the Core version from last time. No changes to supported frameworks due to this.
  • Reorganized a bit of the code internally in case other cart types get supported in the future.
  • Added a couple of fixes for NDS Dragon Quest V carts that have mastering oddities.

v0.2.0

  • Internal cleanup of most of the code.
  • Removed .NET Framework 4.6.1 build.
  • Added .NET Framework 4.8, .NET Core 3.1, and .NET 5.0 builds.
  • Fixed NDS secure areas.
  • Fixed larger game carts.
  • Fixed encrypting N3DS carts.
  • Add force flags for NDS and N3DS.

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

Advertising: