_ModSecurity_™is an open source, free web application firewall (WAF) Apache module. With over 70% of all attacks now carried out over the web application level, organizations need all the help they can get in making their systems secure.
Changelog v2.8.0
Bug fix
New features
Improvements
Regression tests are not able to expect different values according to the platform;
Visual C++ 12/10 runtime dependencies are now part of the IIS installer, no need to have it installed prior ModSecurity installation (Ref: #627);
New script was added to the IIS versions to identify whenever there is a missing dependency (available through the Application Menu);
Memory usage improvement: using correct memory pools according to the context (Ref: #618, #620,#619);
Independent API call to free the connection allocations, independently from the request objects, improvements on Nginx performance, vide issue for more information (Ref: #620, #648);
IIS installer is now using the correct 32/64bits folders to install;
IIS Installer 32bits now refuses to install on 64bits environments;
IIS: Using new WiX options to build the package in the correct architecture;
While installing IIS version the installer will remove old ModSecurityIIS configuration or files before proceed with the installation, avoiding further errors;
CRS from IIS version was upgraded to 2.2.9;
IIS installer does not support repair anymore, in fact it was not working already and it is now disabled;
ModSecurity now warns the user who tries to use “proxy” in IIS or Nginx. Proxy is Apache only;
Remove warnings from the build process (Ref: #617);
Apache configuration in regression tests was changed making it more platform independent;
Reduced the amount of warnings during the compilation (Ref: #385a2828e87897bd611bd2a519727ef88dc6d632, #1e63e49db4a592d28e08a33fc60750c37a3886fe);
Regression tests were refactored to be more Nginx friendly;
Fixed some regression tests that were not being flexible to handle multiple platforms: (Ref #636);
Updates to fix errors found by Parfait static code analysis (Ref: #612);
Cleaning up on the repository, by removing unused files;
IIS installer now supports to perform the installation without register the DLL on the system. It means that the user can download our MSI installer as it was a tarball archive (Ref #629, #624);
IIS now support 32bits and 64bits pools, both are registered on IIS (Ref #628).
Bug fix
github.com/SpiderLabs/ModSecurity/issues/624
github.com/SpiderLabs/ModSecurity/issues/627
github.com/SpiderLabs/ModSecurity/issues/628
github.com/SpiderLabs/ModSecurity/issues/629
github.com/SpiderLabs/ModSecurity/issues/632
github.com/SpiderLabs/ModSecurity/issues/634
github.com/SpiderLabs/ModSecurity/issues/635
github.com/SpiderLabs/ModSecurity/issues/636
github.com/SpiderLabs/ModSecurity/issues/637
github.com/SpiderLabs/ModSecurity/issues/643
github.com/SpiderLabs/ModSecurity/issues/645
github.com/SpiderLabs/ModSecurity/issues/648
github.com/SpiderLabs/ModSecurity/issues/650
github.com/SpiderLabs/ModSecurity/issues/665
github.com/SpiderLabs/ModSecurity/pull/148
github.com/SpiderLabs/ModSecurity/pull/594
github.com/SpiderLabs/ModSecurity/pull/597
github.com/SpiderLabs/ModSecurity/pull/612
github.com/SpiderLabs/ModSecurity/pull/617
github.com/SpiderLabs/ModSecurity/pull/618
github.com/SpiderLabs/ModSecurity/pull/619
github.com/SpiderLabs/ModSecurity/pull/620
github.com/SpiderLabs/ModSecurity/pull/668
github.com/SpiderLabs/ModSecurity/pull/672