Auto PHP Licenser 1.4 brings stronger, OpenSSL-based encryption for future applications and maintains a full backwards compatibility.
Yes, the rumors are true. A short time before publishing a highly anticipated version 1.3 with many changes and enhancements, phpmillion developers started working on a future release. As of today, Auto PHP Licenser 1.4 is ready to download. Beside smaller updates, the most significant is this:
All data encryption modules use OpenSSL instead of Mcrypt;
If you are wondering why this transition is so important, let’s analyze it together. As you may already know, our main goal is not only to protect your code from piracy, but also ensure it’s future-proof. That is to say, all programs secured by our PHP license manager should properly operate on any server around. Today, tomorrow, and many years later. It’s no secret that PHP 5.6, released 3 years ago, is the most used distribution with over 30% of market share in 2017. However, PHP 7.2 (currently in Beta) will remove Mcrypt support in favour of OpenSSL.
What does it mean to you? Nothing, at least now. We expect PHP 7.2 to be the most widely used distribution only in 2021, but it’s never too early to prepare for upcoming changes. Hence, PHP license management software now uses OpenSSL encryption for new installations by default. “But what about existing installations?” – you ask. You can upgrade them as well. And the procedure is easy, too!
First, open the Software Updates window in Auto PHP Licenser to automatically update your installation. Second, download PHP license system, find apl_core_functions.php file in /SCRIPT directory and copy it to your program (overwrite old one). Finally, provide the updated script to your clients. The new licensing module will automatically detect current encryption method and upgrade to OpenSSL if needed.
No changes for server requirements.
Please keep in mind that using OpenSSL-based encryption does not mean you or your client should have SSL certificates installed. OpenSSL is a cryptography library with many different uses; therefore, your code will work perfectly on standard (non-SSL) websites too. If you are worried that such a “new technology” will break compatibility with old platforms, don’t be. OpenSSL encryption and decryption functions are available since PHP 5.3 (released back in 2009), so there’s nothing to worry about.
You don’t need to rush, but be aware that we will drop Mcrypt support in 2018. Hence, if you don’t update your code this year, automatic transition from Mcrypt to OpenSSL in old applications will become impossible. As a result, all the licensing features in old applications will continue working as usually, but you won’t be able to implement new features from future releases. For this reason, we recommend updating your code once you have a chance.
As always, new version comes with full backwards compatibility. It means old applications can connect to v1.4 server and vice-versa; therefore, your clients will not experience any inconveniences during the transition period.