I’m developing some (wordpress) plugins and I’m planning to have a license fee for whoever want’s to use it.
Therefor I need a way to make sure that this plugin is not uploaded to a server where anyone can download it and use it for free.
So I was thinking of using an API key. Valid API key = user can use the plugin. Invalid = plugin does not work.
I’ve looked at this post PHP API Key Generator but I don’t get much wiser of that.
I also know that since it’s PHP, anyone can go into the code and disable API check (I’m just guessing)
What is the best way to secure my plugin? API key? Other ways? Does anyone have link to any good tutorials on the subject?
Advertisement
Answer
If your plugin relies upon interaction with your own server an API key is an excellent way to prevent non-paying users from using it.
However if it doesn’t need to interact with your server then anyone with a little PHP knowledge can modify your plugin to remove the API key check.
A major issue here is the licensing for your plugin. WordPress is GPL, and the GPL has a clause which requires ‘derivative works’ to also be licensed under the GPL. (That’s an understatement: in fact, the whole GPL is based around that clause and wouldn’t really work without it.)
There is a lot of argument about whether a plugin can be considered to be a ‘derivative work’. In my opinion it isn’t, and I think it is unethical to try to force it to be seen as one. However Automattic, the core WordPress devs, and the Free Software Foundation (the organisation which wrote the GPL) claim that WordPress plugins are legally bound to use the GPL and may not use another license.
So far there have been no court cases and so there is no precedent, but there is considerable animosity surrounding a couple of major WordPress plugins which don’t use the GPL, and Automattic has basically threatened legal action whilst the plugin developer has said “please sue me”. Not exactly a pretty situation, and I would say that regardless of the morality of the situation the fact is that the negative publicity normally outweighs the benefits of closed-sourcing a plugin.
To summarise: your plugin basically has to be GPL, which means you have to provide unencrypted source code, so anyone can modify your plugin to remove any restrictions you add. But it should be easy for you to talk most of your potential customers into wanting to buy the plugin from you instead of using a forked version – you can offer benefits such as support, upgrades, etc etc which probably won’t be available for a “cracked” version.
There are several companies which successfully sell plugins, under the GPL and with no protection (API key etc). Even though anyone could in theory just download the plugin and upload it to a public site from which anyone could download it, in practice nobody wants to use an unofficial version which won’t necessarily be updated for new versions of WordPress. So selling plugins does seem to be a viable business model even without protection of any kind.
Of course, all this assumes that someone doesn’t just fork your plugin and carry on maintaining the codebase separately. There’s not much you can do about that – but it’s unlikely to happen.
For what it’s worth, if you’re trying to make life hard for someone who decides to redistribute your plugin, you may like to consider the following :
- you can still claim trademark rights on the name of your plugin even if the plugin itself is open source, so you can legally prevent them from using the same name which your customers know
- only the PHP code in a plugin has to be GPL’ed – you can distribute any files which don’t contain PHP which interacts with WordPress under a separate license to forbid redistribution. For example, CSS, JavaScript, and images don’t have to be under the GPL.