If you want to make a paid PHP plugin, how to avoid being copied to use

For example, I now do a PHP project third-party plug-in, users need to pay a platform to download the use.
The user environment may not be able to access the external network
What are some of the ways that you can solve the problem of "avoiding the ability of a user to copy and use all users after a paid download?"

If you have any relevant experience, I hope we can provide a thought.

The situation now is that the user is not excluded we will push messages to the server, and be happy to use our products, as well as the use of relevant plug-ins. The source code is also encrypted. What to consider is how to protect the developer benefits of paid plug-ins

Additional:
Perhaps I did not make it clear that the plugin user is not a developer, just a simple users. Source code encryption that is sure to do, but even if you source encryption does not affect the plug-in in the application of normal use, right? It is like a single-player game to crack million people use, users do not care about your source code, anyway, I get to use it. This is the kind of situation that you're dealing with

Reply content:

For example, I now do a PHP project third-party plug-in, users need to pay a platform to download the use.
The user environment may not be able to access the external network
What are some of the ways that you can solve the problem of "avoiding the ability of a user to copy and use all users after a paid download?"

If you have any relevant experience, I hope we can provide a thought.

The situation now is that the user is not excluded we will push messages to the server, and be happy to use our products, as well as the use of relevant plug-ins. The source code is also encrypted. What to consider is how to protect the developer benefits of paid plug-ins

Additional:
Perhaps I did not make it clear that the plugin user is not a developer, just a simple users. Source code encryption that is sure to do, but even if you source encryption does not affect the plug-in in the application of normal use, right? It is like a single-player game to crack million people use, users do not care about your source code, anyway, I get to use it. This is the kind of situation that you're dealing with

Encryption method: The PHP files are compiled, you can
Authorization method: Internal to do a verification method, each paying customer will get a key/sn, use the need to enter this key
Verification method: The simple way can be detected according to the address or domain name visited, a key corresponding to an address

The difficulty lies in the internal authentication method, key→ (your private encryption algorithm) → The address that the user will be visited;

In addition, later maintenance may be a bit troublesome. You may also want a universal key for use in the user development phase. You should consider the rest of the design yourself.

Really funny, even if the user is able to use the environment to access the Internet, you can prevent it? Your code is open source, okay? If you implant a recognition statement that will be found and deleted, and if your plugin will proactively push information to a specific server, who dares to use it? What if you stole the core data? Also do not have special consideration of encryption, basically plug-ins will not 100% meet the requirements, so some fine tuning is inevitable, so encrypted plug-ins will not be bought by anyone.

This is still entirely by self-conscious, in fact, the price is very good, we are willing to pay, a few hundred money of the things who will so tangled, and this money is not the programmer himself out, you will ask the boss "we say 500 dollars to buy a copy or use pirated it?" "Or will you tell the boss," we're going to use this, 5,001 copies, to get a piece? " The former boss will not stomach Fei you think the boss's face is not worth 500 dollars?

Finally, pro, I think piracy is not a problem, but no one is willing to use the free is the problem.

Of course, if you do the PHP bottom plug-in compiled mo or DLL words when I did not say anything.

For the modified issue
Your product is encrypted, the plug-in source code is also encrypted, pay to buy the activation code, and then engage in an online activation, late operation does not need to network.

Phar Zend or DLL is confused,
Source code encryption is not what you can do authorization, to obtain relevant information to do serial numbers. It's been cracked, that's GG.

This Windows has not done, there seems to be no perfect solution

Landlord If you pay 300, I personally guess if the sales are good, there will be a development of as long as 50 of the plug-in, so it is recommended

Free, open source is no obligation to donate.

Zend guard~

The core functions are written in python,golang,c or other languages and compiled into executable files for PHP calls.
The verification mechanism is put into it, which increases the difficulty of cracking

PHP7 can be used to export scripts in Opcache.file_cache opcode to some extent to protect the source code and improve operational efficiency.
In fact, sometimes their own slightly confused with Php_strip_whitespace/gzcompress/base64_encode, with Eval/base64_decode/gzuncompress run, anti-defense gentleman or can.

mzphp: The first PHP framework that supports SCSS syntax, CSS sprites, and enphp obfuscation and encryption supports PHP7:
Https://git.oschina.net/mz/mzphp2

