If the sensitive information in the running of the program, such as the registration code, is not safe if it is stored in the global variable, can it be kept in a secret place so that the cracker can not find it and take it out at any time when he wants to use it? After many experiments, the preliminary success has been achieved. This program defines two functions (syz-set1 (x)) and (syz-get1), in which syz-set1 is to save variables and syz-get1 to take out variables.
Detailed usage:
Load syzt-new.fas And then call these two functions.
(load “syzt- new.fas ”）
(syz-set1 8888); secret preservation number 8888
(setq B (syz-get1)); take the saved 8888 and put it into the variable B, and the value of B becomes 8888
This variable can also hold strings and floating-point numbers.
This program is manually modified, variable into acad.exe Somewhere in the process, LSP cannot operate it. If the cracker wants to find it, it is quite difficult.
syzt- new.fas It is decoded. The function name in it can be changed at will, not necessarily called syz-set1. It can be changed to whatever you like.
