Enveloping

Simple Steps to Protection
SecureDongle X Enveloper Tools allows software developers to “Envelopes” any executable files in just a few simple steps. It is simple and the encrypted program will only run if valid SecureDongle X is found.

SecureDongle X Enveloper Tools does not require any programming skills and is an ideal protection solution to secure your applications without posses the source code of your application. This “Enveloping” protection is widely use to protect licensed third party software to prevent unauthorized use or sharing.

Second Layer Protection after API Function Protection
Enveloping protection is also often used to create second layer protection to application which have also implement API security functions. It creates the final outer protection enhancing the security protection of your application.

SecureDongle X includes Enveloping Tools forWin32 PE Executable Files, ..net Executable Files, and Adobe Flash files.

Benefits of Enveloping Protection:

• Protection Application in just a Few Steps
• Protection with No Programming Knowledge Required
• Protect Your Application Without Posses the Application Code
• Enhancing API Function Protected Application

API Functions

Well-Designed API Functions
SecureDongle X provides well-designed API Functions to integrate with your applications, such as Data Hasing Function, RSA Encrypt & Decrypt Function. SecureDongle X API Functions provides flexibilty and higher level security protection to your application.

API Samples
SecureDongle X Software Development Kit includes useful API samples with source codes for all the popular programming languages as listed below:

Access 2000
ASP.net
C++ Builder 6
Delphi 6/7
FoxPro 6
Java
PowerBuilder 6.5/7
Python
Visual Basic 6
Visual C++ 6
Visual Studio .net
etc.

API Functions & Enveloping

Maximizing the Protection
For maximizing the protection to your application, combining both API Functions and Enveloping will bring your application protection to a higher level security protection. We strongly advise this combination protection as a second layer protection to your application with additional Enveloping protection.

To maximize protection using SDX, you could try few tips from us below:

• 1. Use API together with Enveloper if an enveloper exists for your resulting file format. This is a very basic rule. Because our enveloper is already equipped with some anti-debugging and obfuscating methods to prevent common newbie hackers to give up hacking the program. Only using enveloper is also not recommended, because once a hacker can break the enveloper protection in other program, they can also break yours.
• 2. Call dongle APIs in a LOT of places in your application. For example when first start up, when opening a file, when a dialog box opens, and before processing any information. Also maybe do some random checking even when there's nothing done at all.
• 3. Use more than one function to protect a program. Do not just only use find function to look for a plugged dongle.
• 4. Use the encryption functions available in the dongle and tightly bind it with your software to make sure no one tampers with any of your data.
• 5. Use multiple dlls/libraries (if applicable) to call dongle functions. In case one dll is hacked, then there are still other parts of the software that uses the functions from another dll. For example, copying sdx.dll to print.dll, open.dll, and other names, then define the function calls from each dll with different names.
• 6. If you use a dll file to call dongle functions, bind it together with the executable. There are quite some programs capable of doing this; for example PEBundle.
• 7. For increased security, use a system where the information of PC specifications that can run the software is stored in encrypted form inside the dongle, and the application checks it before doing any job. But this method makes the software totally locked to the PC. Even changing one of the hardware might make the software stop running.
• 8. Alter protection method for every new version of the software released. This way even if the old version is hacked, the newer one is still fine.
• 9. Use random checking. For example, just 3 out of 10 checks to the dongle is really confirmed. This is to make the hacker have a hard time deciding whether his hacks work or not.
• 10. If possible, store a part of "script" that your program can run inside the dongle. For example, storing steps on how to calculate interest rate. This script must be used and interpreted by the program to calculate interest rate. If the program fails to find the script in the dongle, then the program can just output a wrong result.
• 11. Use your own anti-debug and other methods of protection, for example applying CRC32 check for the executable and dlls and store the value inside dongle and later get the value and compare the correctness to make sure the program is not tampered.
• 12. Use HID Binding. It's better because even if the seed code of SDX is known, the software will still not run on other SDXs without the same HID. Of course doing this binding makes developers have to change codes each time there is a purchase. So for mass-product software this is not applicable.