Who can provide such a registration machine can only be downloaded once and used once!

snowmanzf

"Just shred the files when you exit" is a clever idea, but there are also problems:
1. What should I do if I copy this file before use?
2. What if the user needs to reinstall the system after redoing?

In fact, the most important thing is how to prevent being copied! difficult! ! Even MS is helpless, what can we do? Looking at the methods used by several major businesses, there are two common methods:
1. Like Rising, the program communicates with the server to prevent excessive registration
Two, hardware dog

vialin

Back tocjly01: This software involves a lot of things, and it needs to write both the server side and the client side at the same time. It requires a lot of debugging. Who will do it for you without payment? We can only provide you with ideas, and the specific implementation still depends on your own research.

cjly01

Is there an easier way to solve the problem, let everyone discuss it again:
The main question now is, how should the user work before and after downloading?
Occasionally there is an idea, is it feasible?
That is, the registrar does not compress decompressed files such as RAR, but can be used (installed) after downloading.
But before downloading, the user has to perform some operations, such as registration, and at the same time, prompt the user: the downloaded one-time registration machine has an identification function, that is, it can only be used on your computer and cannot be copied to other computers. Use it, and then ask him if he wants to download it.
In fact, at this time, the server has already tested some physical characteristics of the computer (such as the serial number of the hard disk), and can assign the user's computer identification code to the one-time registration machine to be downloaded, thereby preventing the use of the registration machine on other computers.
If this method can be implemented, how to code it?

colour220

To solve this problem, we must first consider the consequences of doing so:
1. It is not conducive to the spread and upgrade of software.
Second, it is not conducive to the improvement of the software's own functions, because most of the energy is placed on anti-theft.
3. There is no unopenable lock in the world, which is actually meaningless.

Let me introduce to you the idea of ​​such programming:
1. The choice of algorithm. The algorithm of encryption and decryption involves the difficulty of cracking and the generation of registration codes.
2. Media for generating registration code. It is safest to mark with hardware, and also pack the compiled software to prevent decryption. The software is written into the registry and uses similar Trojan horse functions to disguise system processes and program names to prevent tracking.
3. The registration program is automatically destroyed after the registration code is generated, and a self-deleting tool will be added to automatically detect and delete similar programs in this directory.

If you can do the above three points, your program will be a more successful anti-theft and anti-reuse application~~~~