WP fail2ban - Version 2.2.1

Version Description

  • Fix stupid mistake with WP_FAIL2BAN_BLOCKED_USERS.
Download this release

Release Info

Developer invisnet
Plugin Icon 128x128 WP fail2ban
Version 2.2.1
Comparing to
See all releases

Code changes from version 2.2.0 to 2.2.1

Files changed (2) hide show
  1. readme.txt +8 -2
  2. wp-fail2ban.php +2 -2
readme.txt CHANGED
@@ -5,7 +5,7 @@ Plugin URI: https://charles.lecklider.org/wordpress/wp-fail2ban/
5
  Tags: fail2ban, security, syslog, login
6
  Requires at least: 3.4.0
7
  Tested up to: 3.9
8
- Stable tag: 2.2.0
9
  License: GPLv2 or later
10
  License URI: http://www.gnu.org/licenses/gpl-2.0.html
11
 
@@ -55,7 +55,7 @@ By default, *WPf2b* uses LOG_AUTH for logging authentication success or failure.
55
  Based on a suggestion from *maghe*, *WPf2b* can now log pingbacks. To enable this feature, add the following to `wp-config.php`:
56
 
57
  define('WP_FAIL2BAN_LOG_PINGBACKS',true);
58
-
59
  By default, *WPf2b* uses LOG_USER for logging pingbacks. If you'd rather it used a different facility you can change it by adding something like the following to `wp-config.php`:
60
 
61
  define('WP_FAIL2BAN_PINGBACK_LOG',LOG_LOCAL3);
@@ -106,6 +106,9 @@ to the `[wordpress]` section in `jail.local`.
106
 
107
  == Changelog ==
108
 
 
 
 
109
  = 2.2.0 =
110
  * Custom authentication log is now called WP_FAIL2BAN_AUTH_LOG
111
  * Add logging for pingbacks
@@ -139,6 +142,9 @@ to the `[wordpress]` section in `jail.local`.
139
 
140
  == Upgrade Notice ==
141
 
 
 
 
142
  = 2.2.0 =
143
  BREAKING CHANGE: WP_FAIL2BAN_LOG has been renamed to WP_FAIL2BAN_AUTH_LOG
144
 
5
  Tags: fail2ban, security, syslog, login
6
  Requires at least: 3.4.0
7
  Tested up to: 3.9
8
+ Stable tag: 2.2.1
9
  License: GPLv2 or later
10
  License URI: http://www.gnu.org/licenses/gpl-2.0.html
11
 
55
  Based on a suggestion from *maghe*, *WPf2b* can now log pingbacks. To enable this feature, add the following to `wp-config.php`:
56
 
57
  define('WP_FAIL2BAN_LOG_PINGBACKS',true);
58
+
59
  By default, *WPf2b* uses LOG_USER for logging pingbacks. If you'd rather it used a different facility you can change it by adding something like the following to `wp-config.php`:
60
 
61
  define('WP_FAIL2BAN_PINGBACK_LOG',LOG_LOCAL3);
106
 
107
  == Changelog ==
108
 
109
+ = 2.2.1 =
110
+ * Fix stupid mistake with WP_FAIL2BAN_BLOCKED_USERS.
111
+
112
  = 2.2.0 =
113
  * Custom authentication log is now called WP_FAIL2BAN_AUTH_LOG
114
  * Add logging for pingbacks
142
 
143
  == Upgrade Notice ==
144
 
145
+ = 2.2.1 =
146
+ Bugfix.
147
+
148
  = 2.2.0 =
149
  BREAKING CHANGE: WP_FAIL2BAN_LOG has been renamed to WP_FAIL2BAN_AUTH_LOG
150
 
wp-fail2ban.php CHANGED
@@ -3,7 +3,7 @@
3
  Plugin Name: WP fail2ban
4
  Plugin URI: https://charles.lecklider.org/wordpress/wp-fail2ban/
5
  Description: Write all login attempts to syslog for integration with fail2ban.
6
- Version: 2.2.0
7
  Author: Charles Lecklider
8
  Author URI: https://charles.lecklider.org/
9
  License: GPL2
@@ -67,7 +67,7 @@ function remote_addr()
67
  return $_SERVER['REMOTE_ADDR'];
68
  }
69
 
70
- if (defined('WP_FAIL2BAN_BLOCKED_USERS') && true === WP_FAIL2BAN_BLOCKED_USERS) {
71
  add_action( 'authenticate',
72
  function($user, $username, $password)
73
  {
3
  Plugin Name: WP fail2ban
4
  Plugin URI: https://charles.lecklider.org/wordpress/wp-fail2ban/
5
  Description: Write all login attempts to syslog for integration with fail2ban.
6
+ Version: 2.2.1
7
  Author: Charles Lecklider
8
  Author URI: https://charles.lecklider.org/
9
  License: GPL2
67
  return $_SERVER['REMOTE_ADDR'];
68
  }
69
 
70
+ if (defined('WP_FAIL2BAN_BLOCKED_USERS')) {
71
  add_action( 'authenticate',
72
  function($user, $username, $password)
73
  {