HTTP/1.1 403 Forbidden header on a failed login vs WP Fail2Ban Redux

Send an “HTTP/1.1 403 Forbidden” header on a failed login instead of “HTTP/1.1 200 OK”, which is the WordPress default header on failed login. This is a tremendously simple plugin that does only that and absolutely nothing else. The purpose of this plugin is to provide a way to allow external tools like fail2ban to get a message of a failed login e.g. to prevent a brute-force attack on a firewall level. For the public domain. Uses PHP5.3 anonymous functions and will not work on earlier versions of PHP

WP Fail2Ban Redux records various WordPress events to your server’s system log for integration with Fail2Ban. This plugin is (mostly) a drop-in replacement for WP fail2ban by Charles Lecklider. While WP fail2ban is a great plugin, there are a number of improvements that could be made. In order to facilitate these improvements, a major refactoring of the codebase was necessary. The core functionality between WP Fail2Ban Redux and WP fail2ban remains the same. WP Fail2Ban Redux is considered to be mostly a drop-in replacement, because all constants have been replaced with filters, and will, possibly, require some upgrade work. Don’t work it’s as simple as implementing the constants. The following events are recorded by default: Failed XML-RPC authentication attempts. Successful authentication attempts. Failed authentication attempts — differentiated by a user’s existence. Pingback errors. The following events can be enabled via filter: Pingback requests. Blocked user enumeration attempts. Authentication attempts for blocked usernames. Spammed comments. Extra documentation is available on the WP Fail2Ban Redux GitHub Wiki.