Since coming out of beta, Let’s Encrypt have actually made these limits more generous, and unless you have a particularly crowded server or collection of subdomains, you’re probably unlikely to come up against a ceiling.Pretty much the one advantage of my solution was the bundling of subdomains and aliases into a single SAN.
It’s almost always best to stick with the native solution rather than a third party one (particularly when the third party one is developed by a time-poor hacker), and that rule largely applies here.
The first issue is addressed easily enough – you need to create a site for the domain used by the control panel (if it doesn’t already exist), mark it for SSL with Let’s Encrypt and then symlink your ISPConfig interface certificates to the freshly pressed certs used by the site.
It appears that Apache 2.4.10 came out 2014-07-21, just before my last update. Would the warnings from rkhunter and sucuri be false alarms? Thanks, OHAs those tools only check the version (2.2.15), and thus can not determine the exact patch level from upstream, it usually is a false alarm (as you can't compare the version in EL6 with the vanilla version from apache (see backporting).
As those tools only check the version (2.2.15), and thus can not determine the exact patch level from upstream, it usually is a false alarm (as you can't compare the version in EL6 with the vanilla version from apache (see backporting). It seems that backporting fixes the security issues and the only reason to update to 2.4 would be to get newer features.
“Build your own registration form copy one of the existing files (ispconfig_register_or ispconfig_register_free.php) change the php class name to «Ispconfig Your Class» for example rename the file to «ispconfig_your_class.php».