Bad Behavior 2.0.23
August 24th, 2008 by Michael Hampton
Bad Behavior 2.0.23 has been released. It is a maintenance release and is recommended for all users.
MediaWiki and WordPress users should take note of special upgrade instructions below.
Who should upgrade?
Users who implement OpenID should upgrade. Users whose sites are targeted toward smart phones and other wireless devices should also upgrade.
What’s new?
New in this release (since 2.0.22):
- A PHP OpenID library was being blocked. It is now permitted. This should resolve OpenID issues for a wide variety of sites. Please contact me if you continue to have OpenID trouble. (Thanks to Christian Höltje for the patch.)
- A new Google search crawler for mobile content was inadvertently blocked. It is now permitted.
- Several harmless PHP notices have been suppressed. (Thanks to Amilcar Lucas, webmaster of KDevelop.org for the patch.)
Support
If Bad Behavior has helped you, please make a financial contribution toward further development. Your contribution ensures that I can prioritize Bad Behavior development. Otherwise I must spend most of my time on other projects which pay the bills. Which is a shame, because I really enjoy making spammers miserable and drying up their revenue streams until it’s more profitable for them to work at McDonald’s than to send spam.
Download
Special Upgrade Instructions
Users of MediaWiki and WordPress upgrading from version 2.0.20 or earlier should follow these special directions (from 2.0.21 or later, upgrade normally):
For MediaWiki: Before installing this version of Bad Behavior, manually remove (e.g. using FTP or ssh) any old versions you may have, including the lines added to LocalSettings.php. Then install the new version fresh, following the installation instructions for MediaWiki.
For WordPress: If updating to this version through the automatic updater fails, manually remove (e.g. using FTP or ssh) any old versions you may have installed. Then upload and install the new version fresh, following the installation instructions for WordPress. After doing so, future automatic updates should proceed normally.
For other platforms: No changes to your upgrade procedures should be necessary.
Robert@PNG Says
Excellent work!
Upgraded to 2.0.23 without any problems.
Thanks.
R
Aug 24th, 2008 at 10:53 pm
phototristan Says
I just discovered this plugin and must say, I’m VERY impressed.
My current WordPress blog is only a couple of months old and I had over 500 comments that were caught by Askimet.
The fact that Bad Behavior will prevent most spammers from even being able to leave a comment in the first place is really nice. And, since installing it, I’ve seen a marked decrease an spam in my Askimet queue!
Aug 29th, 2008 at 5:40 pm
william Says
I found out about Bad Behavior through a programmer working on making SubDreamer a better product, then I came across the plug application for phpBB forums (phbadbehave2). It seems this is terribly outdated and I was curious if someone were going to update this or at least point me out to where I could find an implementation of this product for phpBBv3 using the latest version of Bad Behavior. Thanks in advance! William
Sep 17th, 2008 at 5:30 pm
Peter Says
does disabling http request logging affect the functionality of this plugin?
Sep 17th, 2008 at 6:35 pm
Michael Hampton Says
Yes. Some requests are logged in order to compare them to future (e.g. minutes later) requests from the same IP address in certain circumstances. You will receive more spam if you disable logging entirely. (But it is safe to disable verbose logging.)
Sep 18th, 2008 at 4:09 am
Peter Says
thanks Michael, I have re-enabled logging. I was concerned about large log files taking up space on my server, but if it affects the functionality of bb i will leave it on.
Sep 19th, 2008 at 12:31 am