Remove XML-RPC Methods vs WP Fail2Ban Redux

Removes all WordPress methods from the XML-RPC API to increase security. It does more than just using the xmlrpc_enabled hook, because that is only used “To disable XML-RPC methods that require authentication”. Activating this plugin will also disable pingbacks, trackbacks, and Really Simple Discovery (RSD), because these rely on XML-RPC. It works with any webserver, because it does not use the .htaccess file. Testing the plugin From the command line you can test if the plugin is working correctly using curl. Replace the example.com link to match your website: curl -d ' system.listMethods ' https://example.com/xmlrpc.php This should only return the following methods: – system.multicall – system.listMethods – system.getCapabilities

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.