Ways To Make Your Software Hacker-Proof and Crack-Proof
CryptoLicensing uses the latest military force, state-of-the-art technology, encryption techniques to safeguard and unbreakable code license to verify that your software and intellectual property is protected. Cryptographic licenses are unbreakable, even with brute force, the power. In addition, since the certificates can be issued only with the private key (which you have), this means that it is impossible for a hacker to develop a “keygen” (generator) your software. This is an excellent first line of defense. It is yours for the next line of defense. Below is some helpful tips and guidelines for the effective management of licenses and effectively CryptoLicensing written confirmation license code with the API CryptoLicensing validation. The philosophy is simple: as difficult as possible for pirates on the “Crack” of your software, leading to what pirates to lose interest in your software or not, it is worthwhile for him / her.
Check license occasions
Instead of checking the software license to run only on whether the license on several points, the time during the execution of software and several places in your code. Not to use a single license confirmation routine in your software. Check if a license to different places in the software, but not a single license confirmation routine to do so. This ensures that hackers can not bypass your system licensing piracy simply a piece of code in your software and the strengths of the intruder, for each piece of the validation of the license in your code program.
Use multiple layers of control of licenses
In addition to the normal license confirmation each time your software is running, add another layer, which checks if a license, if a certain criteria is uncertain. You can, for example for a license on the 2nd Monday of the month, or every 63 days, or on February 29 in a leap year. If a hacker bypasses the normal code of the license, the “guerrilla” layer is always present, whether a license and make the box to fail.
Use encrypted dlls
Move some of your software in a DLL and the DLL to encrypt with a key. When generating certificates CryptoLicensing press the button of your license code (use of its user data for these CryptoLicensing) and decrypt dll with this key before using it. This ensures that even if an attacker bypasses the code of your software license does not work properly because they are not able, for the DLL file encrypted.
Make sure the hash of the EXE / DLL to detect tampering
You can hash / checksum your exe / dll in your license code from the CryptoLicensing (use of user data for this CryptoLicensing). If your EXE / DLL is loaded, you can create a new hash calculation of the exe / dll, and compare them with the license code. If other, it means that your exe has been tampered with or altered. As well as license verification, perform this check box to several points of time and place of your software.
Not display the error on
If a license fails, indicates that this is not immediately to the user that the verification has failed. Instead, expect other software to run and gives the user. This makes it difficult for hackers to locate and bypass the control of your license.
Do not use explicit error messages
During registration a user license is not checked, do not use an explicit and clear messages like “invalid license”. Instead of a generic error message and ask the users, contact your support personnel. He can not know the cause of the error is not a license check, and the contact, you can try one of the processing and sale of the illegal exploitation of licensed users to a user or an intruder, s it is with you.
Crash or not, or output incorrect results when license fails
In combination with the two above, if a license fails, or if you find that your software has been hacked or your licensing system has been compromised, and write them down if your treatment of some at a later date, you can use your software incidents or output incorrect results. Sometimes an intruder may be in your best interest to lose “Buggy” program that is not as informative display of error messages!
Insert the user information, certificates
When generating certificates, embed some data on users of the license, as the user name, e-mail or company name (use of user data for this CryptoLicensing). See the information visible in several places in the software. It is a very effective means for users, it has the license code with others.
