Hi Keith, I put in a 5s default so that it …

By 28th March 2024 Uncategorised

Comment on WordPress Login Cool Down – Stops brute force attacks on WordPress the easy way by Paul G..

Hi Keith,

I put in a 5s default so that it wasn’t too high to annoy folks that don’t usually change default settings.

I think the longer you can set it, the better. Obviously though, the higher you go, the less payoff, but 30 seconds is a good number, and if you can go for higher, you should. It really depends on how many users you’re likely to have logging in because this cooldown is not per-user, but for the whole site.

I’m delighted to hear you’ve been have a great experience with the plugin – we love to hear that! ๐Ÿ™‚

Thank you!
Paul.

Recent Comments by Paul G.

Security: Hide The WordPress Login and Admin Pages (wp-login.php)
Hey Rob,
Brilliant news… Glad it’s working so well for you!


Part 5: Ultimate Comment SPAM Killer – Shield WordPress Security Plugin
Why does WordPress need to do that? I’ve no idea… that’s the way the author of this particular code decided to implement this. ๐Ÿ™‚

My approach is to take each “spam” word/pattern and I use “stripos()” on each item of the comment that needs to be checked.

The truth is that efficiency isn’t hugely important in this area because it’s only run when a comment is posted. I could probably optimize my approach too, but again, it’s not critical.

Further reading: http://lzone.de/articles/php-string-search.htm


Part 4: Login Protection – Shield WordPress Security Plugin
There’s nothing you can do about that unfortunately if the bots are cracking away at your page. Most bots would get blocked by the automatic blacklist if they’re repeatedly hitting you with this.

As to XML-RPC, we have a couple of options ranging from by-passing the login/user sessions systems to completely disabling it:
https://www.icontrolwp.com/2015/10/automatically-block-brute-force-amplification-attacks-against-wordpress-xmlrpc/


Further WordPress Admin Access Lockdown
Eileen, Lynn,

The automatic updates system is WordPress-controlled and run on a WordPress cron. The Security admin access shouldn’t affect this. If you have enabled automatic updates, but restricted the system using the admin access and you find it’s not working as it should, please let me know in the support forums.

To your first question, if you enable this Security Admin system and lock-down any features, then you must, as an administrator or not, authenticate with the Security Admin system before you can make changes to the zones that have been restricted.

Let me know if it’s still unclear and I’ll elaborate further on areas you need.
Thanks!


Part 5: Ultimate Comment SPAM Killer – Shield WordPress Security Plugin
This is something that you’ll have to test with your particular installation(s) and configuration. Aggressive page caching will probably affect this functionality, but that is the double-edged sword that is “caching”.

I’d be interested to hear what you find with your tests.

Thanks!


x Logo: ShieldPRO
This Site Is Protected By
ShieldPRO