The shell protection provides a fast and easy way to protect your application. It uses various techniques to modify and wrap the executable that can create the protected application instantly, without having to modify the source code. The shell protection supports a wide range of the most common executable file types for DOS, Win16, Win32, and Win64 applications. However, you might find that ElecKey Integrator cannot integrate the shell protection into your application. Or, the Integrator may create the protected application, but it does not function properly as the original. This might be because the protection settings are not right, or the shell protection does not support your executable file type. The following provides a guideline to help you adjust the settings. So you can integrate the shell protection into your application successfully.
When using ElecKey Integrator to protect your
application, it automatically determines the applicable methods and options.
·
By default, the Injection-1
protection method is chosen first. If there is any problem, try disabling
either or both options: Enable Shell Protection
Optimization and Enable Code Section
Encryption to Protect Against Decompilation,
under the Protection Options
dialog box / Main
tab.
·
If the Injection-1 method is not successful,
try switching the protection method to Injection-2,
under the Protection Options
dialog box / Main
tab. If there is any problem, also try disabling either or both options: Enable Shell Protection Optimization and Enable Code Section Encryption to Protect Against
Decompilation.
·
If both Injection-1/2 methods are not
successful, try switching the protection method to EXE Scramble,
under the Protection Options
dialog box / Main
tab.
If none of the above is successful, it is likely that that the shell
protection does not support your executable file type. You may consider using the Instant
KeyCheck API or the KeyCheck API, instead of the shell protection.