DcryptDll plug-in: Difference between revisions

From NSIS Wiki
Jump to navigationJump to search
m (Added the algorithm name used.)
mNo edit summary
Line 14: Line 14:
== Description ==
== Description ==


These add encryption / decryption capability to NSIS using the [[Wikipedia:ARC4|ARC4]] algorithm.
These add encryption / decryption capability to NSIS using the [[Wikipedia:RC4|RC4]] algorithm but it can also hash the string with the [[Wikipedia:MD5|MD5]] algorithm.


In a manner similar to the ExtractDllEx plugin, one program is used on the computer
In a manner similar to the ExtractDllEx plugin, one program is used on the computer

Revision as of 14:17, 20 November 2005

Author: Arrby (talk, contrib)


Links

Download link:

DcryptDll.zip (172 KB)

The .zip file above includes a Plugin for NSIS (DcryptDll.dll) and two executable binaries (Ncrypt.exe & GenKeys.exe), the source to build all 3, two example .nsi scripts showing possible usage, the how to use document DcryptDllReadme.html, and a couple of other supporting files.

Description

These add encryption / decryption capability to NSIS using the RC4 algorithm but it can also hash the string with the MD5 algorithm.

In a manner similar to the ExtractDllEx plugin, one program is used on the computer you are compiling your NSIS script on to do the encryption, and the plugin is used to do the decryption when the Installer .exe is actually executing.

Ncrypt.exe is the program you use for the encryption, DcryptDll.dll is the plugin used to do the decryption.

The NGenKeys.exe is not necessary, but is included for convenience: you can use it to generate the KeyStrings you will need for encrypting and decrypting the files.

The zip file was built so that you can just extract it (preserving folder names) to your NSIS distribution Contrib folder. You should either move the plugin to the Plugins folder or recompile the source (the VC++ 6.0 project file has output set to the Plugins directory).
You can move Ncrypt.exe and NGenKeys.exe to some folder included in your PATH environment variable or whatever.

Please let me know if you find any of those "dreaded" bugs.