More questions about BruteProtect and why won't IP blocking work?
-
I have some of the same concerns as tomdkat. I just installed BruteProtect on a multisite a few days ago but I have some questions too.
How does BP work? If it suddenly goes haywire, what do I tell my hosting company? Although BP has brought down my usages stats dramatically, I am still a bit skittish. I spent a lot of time on your website trying to find out how BP works but there are no clues I can find.
Despite the reduction in brute attacks, there are still brute force attempts and I would encourage anyone who is using this plug in to look at their raw access logs to find login attempts. In the past 24 hours, my usage logs show nearly 72,000 attempts to login from 167.114.42.112 which belongs to OVH which according to ROKSO is a very bad player. A couple of days ago I had nearly 4,000 login attempts from 83.64.251.157, another suspicious source, over a 24-hour period soon after installing BP. Although I have added these IP#s to my deny list in .htaccess they are still hammering away and not being denied their attempts.
If deploying BP means you lose control of your denied IPs in .htaccess I believe you have a duty to notify folks of this before they install BruteProtect. If you don’t, then my host has some explaining to do.
- The topic ‘More questions about BruteProtect and why won't IP blocking work?’ is closed to new replies.
