PHP: Authorization Code feature development

The ability to develop an authorization code is required for the project.
The customer will only be able to use it after obtaining the authorized documents.
Currently using PHP's built-in library: MCrypt, wrote a class.
But it is still too simple, decryption class placed on the client machine, easy to be cracked.
Ask everyone to help out the idea.

Reply content:

The ability to develop an authorization code is required for the project.
The customer will only be able to use it after obtaining the authorized documents.
Currently using PHP's built-in library: MCrypt, wrote a class.
But it is still too simple, decryption class placed on the client machine, easy to be cracked.
Ask everyone to help out the idea.

To add the most difficulty to client-side cracking, imitate Microsoft on the network activation bar. Or I've seen a client-server architecture for desktop software, equivalent to a customer renting a machine to a developer.

But listen to me: The crack in the end is just a few instructions to bypass the genuine check, nothing difficult . Do not know what your application is, but for the general application, through the software rolling upgrade, technical support and other added value, to increase the willingness of customers to purchase genuine, more than a variety of static anti-cracking means more effective.

As powerful as StarForce, it is only a matter of time before a generation breaks out.

Source code encryption on the line. Recommended Zend, other tools are slag residue. After the encryption, casually toss.

