Compatibility with Ninja WP Firewall and/or Brute-Force Login Protection
-
I have been using both Ninja WP Firewall and Brute Force Login protection, with BF set to catch brute force earlier than NWPFW, since that adds the offending IP to the .htaccess immediately. However, I have noticed that the .htaccess deny list gets very long very rapidly, which I suspect bogs down the site access.
I wrote a script which downloads the deny list and abbreviates it by removing the last octet of each IP address and removing duplicates. I figure that removing the last octet is unlikely to block any legitimate user (if you think I’m wrong about that, please let me know why), since I often see BF attacks coming from sequential IP addresses, and figure those are just cycling through a proxy.
However, running this process (even if only once per month) is labor intensive, and somewhat error-prone, especially since I have several sites that get frequent BF attacks. I would definitely like a set-and-forget defense that just works. Plus, BFLP and NWPFW do not block splog/spam registrations.
And the plugin I use to remove spam registrations has not been updated recently, and does not appear to work with 4.4.1
How does your plugin differ from BFLP and NWPFW? Is your plugin compatible with those, or do I need to remove them?
TIA!
- The topic ‘Compatibility with Ninja WP Firewall and/or Brute-Force Login Protection’ is closed to new replies.