So, encryption is good, depending on how you call the encrypted module, how to effectively integrate the encryption module and your program. I am afraid that there are not a few decryptors will analyze the internal conditions of the DC, as long as they understand the interface. Due to the decline in chip prices, the current encryption lock uses a chip for smart cards. In theory, this encryption lock can not be decrypted. But this is theoretically, in fact, no one can use the encryption lock to this level. Or the above problem, you must confuse the interface to the degree of decryptors that cannot understand. You always need to judge the data returned by the interface! I want to think about it, and the registration machine like ACDSEE has worked hard, the average number of encryption locks, the decryption person, after the IDA analysis, almost a glimpse. If you don't know, use OD dynamic tracking. In particular, the encryption lock company module, most of the anti-tracking functions, that is, it is easy to take back with their EXE PACK to compress it, it is very easy to prevent Ida analysis and OD tracking. After saying half a day, the conclusion was there for thousands of years. It is the universal truth that everyone knows, and the contradiction is universal, and it is necessary to strive to struggle to overcome the contradiction. In other words, overcome the contradiction of the decrypted needs you need to spend a big effort. Nothing is a good way to let you solve this problem easily, please keep in mind this truth. I can only give you two suggestions: 1. Study yourself to decrypt, self-learning, become an encrypted master 2. Ask the encrypted master, let them help you encrypt the skill when it is concrete, and there are more important 1. Script language like VF PB is more difficult to decrypt, maybe it is possible to use 2. For compilation languages, it must make the criterion, disperse, and the code is chaos. This is the opposite of this and software engineering. I don't understand yourself, and it is more difficult to understand after others. 3. If you use C C , use a local function pointer to call the encryption function. Multi-use global variables, it is best to use a certain bit of the structure, rather than a single INT. 4. Add some spam code confused 5. Let your encryption algorithm have different performances on different machines, so it is difficult to use on other machines on a certain machine. For example, some data is generated according to the characteristics of the machine, and then use this data. 6. Add a shell to your own program. It is recommended to use the ASPR2.0, use the SDK and shell communication inside, and use all options to encrypt. 7. It is very desirable to not be decrypted and not afraid of compatibility. I think even if it is all, everyone is not easy to understand. Moreover, it is easy to do. Finally, repeat, there is nothing a good way to make it easy to solve this problem.
