Bad Behavior 2.2.1
February 1st, 2012 by Michael Hampton
Bad Behavior 2.2.1 has been released. This is a maintenance release and is recommended for all users.
Who Should Update?
All 2.2 series users should update in order to receive the important bug fixes contained in this release.
Users who have not yet updated to the 2.2 series should plan to update as soon as possible. Support for the 2.0 series will end June 30, 2013.
Download
What’s New?
Changes since 2.2.0:
- On platforms where database logging is available, Bad Behavior would sometimes continue to log even when the logging setting was turned off. This has been fixed.
- When a site enabled the Reverse Proxy option when it was not actually needed, Bad Behavior would sometimes fail to acquire the correct IP address for incoming requests. Bad Behavior’s code to detect this situation and acquire the correct IP address has been improved.
- WordPress: When a different anti-spam plugin identifies a request as spam, and Bad Behavior did not, Bad Behavior will now log a copy of that request (if logging is enabled). This is to help facilitate reporting of spam not yet detected by Bad Behavior. WordPress users may view the log by visiting the administrative page Tools » Bad Behavior Log.
- WordPress: To improve compatibility with other plugins, Bad Behavior no longer stores data in PHP sessions while screening requests.
Support
I will skip the usual speech. If you’re reading this you already know how valuable Bad Behavior is. Donate today to ensure that I can keep going in the fight against our mutual enemies, the spammers.
Will Says
I just autoupgraded my BB to 2.2.1 on my WordPress install. After the upgrade it broke my site.
It appears there’s a mistake in bad-behavior-mysql.php on line 27 where a ] is omitted, which breaks everything. Adding the bracket fixed it.
Feb 1st, 2012 at 10:55 am
Michael Hampton Says
Thanks for letting me know. I’ve pushed an update to svn and it should be up in about 15 minutes.
Feb 1st, 2012 at 10:56 am
w Says
Did you change the version number? How do we know it’s the repaired version?
Feb 1st, 2012 at 5:03 pm
PJH Says
“Did you change the version number? How do we know it’s the repaired version?”
[x@s15474768 bad-behavior.2.2.1]$ grep BB2_VERSION *
core.inc.php:define(‘BB2_VERSION’, “2.2.1″);
[x@s15474768 bad-behavior.2.2.1]$
Feb 2nd, 2012 at 12:51 pm
butchs Says
I blocked the following code from my port:
/* if (array_key_exists(‘Cf-Connecting-Ip’, $package['headers_mixed'])) {
require_once(BB2_CORE . “/cloudflare.inc.php”);
$r = bb2_cloudflare($package);
if ($r !== false && $r != $package['ip']) return $r;
# FIXME: For Cloudflare we are bypassing all checks for now
# See cloudflare.inc.php for more detail
bb2_approved($bb_settings, $package);
return false;
} */
I did this because when you disabled the “cloudflare.inc.php” test the above code stops testing when CloudFlare is being used, bypassing the remaining BB tests.
Feb 5th, 2012 at 2:02 am
Collector Says
My log is now dirty with tons of:
PHP Notice: Undefined index: reverse_proxy in /bad-behavior/bad-behavior/core.inc.php on line 85
I’ve changed
if ($settings['reverse_proxy']) {
to
if (!empty($settings['reverse_proxy'])) {
Please fix the code.
Thanks
Feb 5th, 2012 at 8:36 am
Michael Hampton Says
What platform are you using?
Feb 5th, 2012 at 8:43 am
Roger Due Says
I really appreciate all the work you have been doing and use Bad Behavior on all of the WordPress sites I work with and recommend it to others.
REQUEST: Since you are already monitoring all of the IP addressed, I would like the ability to specify a specific IP address that you would also BLOCK.
I am also using the “Limit Login Attempts” by Johan Eenfeldt and recently over a period of 2 weeks someone was trying to crack the the wp login for one of my sites.
Yes, there is a plugin I could use to block an IP or range of IP’s, but it seems as though you are already looking at this information, so it would be great if you could provide a BLOCKING service in one of your future updates.
– Thanks
Feb 16th, 2012 at 12:21 am
San Says
Bad Behaviour v2.2.1 still blocking googblebot.
From Log:
2012-02-21 22:00:45
User-Agent claimed to be Googlebot, claim appears to be false.
GET /guest-reviews/ HTTP/1.1
Accept: */*
Accept-Encoding: gzip,deflate
Connection: Keep-alive
From: googlebot(at)googlebot.com
Host: http://www.bedbreakfastprovence.com
User-Agent: Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)
X-Bad-Behavior-Remote-Address: 66.249.xx.xxx
Note:
No strict checking
Reverse Proxy enabled, coz I also use W3 Total Cache and MaxCDN.
Feb 21st, 2012 at 10:15 pm
Michael Hampton Says
San, you do not have a reverse proxy and need to turn the option off.
Feb 22nd, 2012 at 12:40 am
San Says
Thanks, the description given below that feature was not clear to me.
Also noticed new release, thanks for great support.
San.
Feb 22nd, 2012 at 8:45 am