BFM: mod_security scans not triggering IP block (SECURITY)

Version 1.62.0


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 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/ file.

Try DirectAdmin with a 30-day money back guarantee!