Write a myriad of WordPress events to syslog for integration with fail2ban.
fail2ban is one of the simplest and most effective security measures you can implement to prevent brute-force password-guessing attacks.
WP fail2ban logs all login attempts - including via XML-RPC, whether successful or not, to syslog using LOG_AUTH. For example:
Oct 17 20:59:54 foobar wordpress(www.example.com): Authentication failure for admin from 192.168.0.1 Oct 17 21:00:00 foobar wordpress(www.example.com): Accepted password for admin from 192.168.0.1
WPf2b comes with two
wordpress-soft.conf, designed to allow a split between immediate banning and the traditional more graceful approach.
Requires PHP 5.3 or later.
CloudFlare and Proxy Servers
WPf2b can be configured to work with CloudFlare and other proxy servers. See
WP_FAIL2BAN_PROXIES in the FAQ.
WPf2b can log comments. See
WPf2b logs failed pingbacks, and can log all pingbacks. See
WP_FAIL2BAN_LOG_PINGBACKS in the FAQ.
WPf2b can log comments marked as spam. See
WP_FAIL2BAN_LOG_SPAM in the FAQ.
WPf2b can block user enumeration. See
WP_FAIL2BAN_BLOCK_USER_ENUMERATION in the FAQ.
Work-Arounds for Broken syslogd
WPf2b can be configured to work around most syslogd weirdness. See
WP_FAIL2BAN_HTTP_HOST in the FAQ.
WPf2b can be configured to short-cut the login process when the username matches a regex. See
WP_FAIL2BAN_BLOCKED_USERS in the FAQ.
Requires: 3.4.0 or higher
Compatible up to: 4.6.0
Last Updated: 6 months ago
Active Installs: 20,000+
0 of 2 support threads in the last two months have been marked resolved.
Got something to say? Need help?