DirectAdmin Modsecurity changes in Apache
DirectAdmin 1.691 release has modsecurity part refactored. It uses a different method to enable the modsecurity for the apache webserver.
- the
httpd-modsecurity.confis now included with thehttpd-modsecurity-enable.confthat gets generated dynamically, not with thehttpd-phpmodules.confas before httpd-modsecurity-enable.confis always included by the httpd.conf. That file is empty when modsec is disabled, and filled with includes when enabled.libxml2.sois not used in apache configs anymore as it’s not needed for modsec in 2.4.
If you receive an error like this:
|
|
You have custom files in your /usr/local/directadmin/custombuild/configure/ap2/conf/ directory. Please note, as soon as you start customizing the configs - you become responsible tracking the changes.
Recommendation is to review the configs (diff with the current configs in /usr/local/directadmin/custombuild/configure/ap2/conf ) or remove the customizations completely.