BFM: mod_security scans not triggering IP block (SECURITY)

Version 1.62.0

Bugfix
Finished

If you've enabled the brute_force_scan_mod_security_logs=1 to block IPs that have too many failed mod_security connections (it's off by default), the feature was logging the entries, but not adding to the count for the block decision. An entry was being made into the brute_ip.data file, but it was not specifying which service was being blocked (json formatted checks had the bug, only mod_securiity at this time) Fix properly adds the mod_security1=# / mod_security2=# to the data/admin/brute_ip.data file.

Interested to try DirectAdmin? Get a 30-day Free Trial!