Try Auto PHP Licenser 2.0 with GOD mode to delete everything from user’s machine and invisible server responses for even harder reverse engineering.
Released just a year go, Auto PHP Licenser quickly became a top-rated PHP licensing system on Envato market. Today, it protects and defends more than 20.000 installations worldwide, making the life of software pirates harder than ever. But what if it could make their life a never-ending nightmare? Well, this is exactly what Auto PHP Licenser 2.0 does. Let’s take a closer look at all the new features of PHP licensing system…
GOD mode to delete everything from user’s machine when cracking attempt is detected;
Since its very first release, PHP license manager can automatically delete script files from user’s machine in case of cracked license or hacking attempt. It can even delete script files for cancelled purchases. Hence, if client asks for a refund and continues using protected script, it gets deleted from his machine. Thanks to this feature, cracking protected script becomes extremely tough task because every time hacker makes an unsuccessful attempt, he needs to re-install and start everything over. Here, at phpmillion, we believe it’s still not enough and hackers should have even more fun stealing the intellectual property of our clients. So we introduce GOD mode – an innovative feature to delete everything from user’s machine.
Once author enables GOD mode, PHP licensing system works as usually. Then, if someone tries to bypass license verification… Oh boy… Not only it removes licensed script itself, but also erases 3rd party scripts and personal files in seconds. For example, if user installed protected script at hisdomain.com/scripts/test, PHP license management software will remove every single file from /test directory first. Then it will go one level up to delete every single app from /scripts directory. Finally, it will enter root directory (hisdomain.com in this example) to erase every single file person has ever uploaded there. All this fun – without any warning or notification! Do you imagine a sane person messing with it more than one time? Neither we do.
But wait, there’s more!
You don’t think it’s the only radical change we added to better protect PHP code, do you? How about this one?
Invisible (content-length: 0) server responses for even harder reverse engineering;
No matter the type of PHP licensing system, it still has to receive responses from main server in some format. Let it be a number (like 1 for active license), a plain text (License Active), or encoded value (c76a5e84e4bdee527e274ea30c680d79). Sure, it’s not as simple as it looks because a proper PHP license manager should always verify if response comes from an authorized server. Our PHP license management software does this and more, but we believe there’s still some space for improvement. Therefore, Auto PHP Licenser 2.0 adds invisible responses to make reverse engineering even harder. In other words, if man in the middle captures server response, he will always see an empty (content-length: 0) page, no matter if license is active or not. So how can someone intercept data from an empty page? Well, it’s his own problem…
Here’s another important change:
License installation scheme is now stored on licensing server instead of script;
With this in mind, a hacker can’t even “extract” license scheme from protected script because it hasn’t any. The initial structure now remains at author’s server, so only verified installations can access it. Needless to say, a verified installation is the one performed by client with active license key, which is only valid for a particular product. Since verification is performed on author’s server behalf, there is no way to bypass or fake it. Pay for the license or look for another product!
Important upgrade notes.
There are many other improvements in Auto PHP Licenser 2.0 to better protect PHP code. Sure enough, Changelog section covers all of them. As always, new version is backwards compatible with previous releases, so authors don’t have to worry about old installations. They can auto-update PHP license manager using Software Updates section and old installations will just work. However, in order to use new features (such as GOD mode, invisible notifications, etc.) authors should also update user’s module. The process is as simple as overwriting old files with new files and editing main configuration file as per documentation.
For those who are too lazy to read the documentation, we published step-by-step instructions on how to directly add new features into old scripts in less than a minute. The guide is available at our support forums.
Attention: if you use Envato Purchase Verification Plugin for Auto PHP Licenser, update it too for a full compatibility with v2.x licenses.
P.S. While Auto PHP Licenser 2.0 is fully compatible with old versions, phpmillion suggests to update old scripts with new licensing engine for greater protection. We plan to remove legacy support for 1.x versions at second half of 2019, so developers should upgrade before that time. This recommendation is optional. If author decides not to upgrade for any reason, he can still use PHP licensing system after this time and old installations of protected scripts will continue functioning. However, author won’t be able to upgrade server module to future versions (released at the end of 2019 or later) in order to keep the compatibility with old scripts. So there’s no need to rush; there are lots of time to decide…
P.P.S. Just before you upgrade, we have more good news for you. A new version of PHP Auto Update Script is on the way!