Integration with vBulletin - vB Bad Behavior

/**
* vB Bad Behavior is free software; you can redistribute it and/or modify it under
* the terms of the GNU Lesser General Public License as published by the Free
* Software Foundation; either version 3 of the License, or (at your option) any
* later version.
*
* This program is distributed in the hope that it will be useful, but WITHOUT ANY
* WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
* PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details.
*/

What is vB Bad Behavior?
This is an integration of the Bad Behavior software with vBulletin.

What is Bad Behavior?
Bad Behavior is a PHP-based solution for blocking link spam and the robots which deliver it. Bad Behavior complements other link spam solutions by acting as a gatekeeper, preventing spammers from ever delivering their junk, and in many cases, from ever reading your site in the first place. This keeps your site's load down, makes your site logs cleaner, and can help prevent denial of service conditions caused by spammers.

Visit http://bad-behavior.ioerror.us/ for more.

Features
For more information on the features of Bad Behavior (and subsequently this mod) please go to Bad Behavior's site:

http://bad-behavior.ioerror.us/documentation/benefits/

For features related to the mod itself, please take a look at the screenshots.

This mod should work with the entire 3.x series (well, beginning with 3.5), but it's only been tested on 3.8.x. I'm not sure if this works on vB 4.x yet, as I've not tested it - but if you try it out, let me know!

Installation
1. Extract the contents of the zip file.
2. Upload the contents of the `upload` folder to your forum root.
3. Enter your AdminCP and go to Plugins & Products > Manage Products > [Add/Import Product]
4. Import the product using the `product-vb_badbehavior.xml` file.
5. Configure the mod in AdminCP -> vBulletin Options -> vBulletin Options -> vB Bad Behavior Options

Upgrading

vB Bad Behavior
In many cases, all you'll need to do to upgrade is follow the installation instructions above.

The only difference, will be you'll need to allow the files to overwrite. Also, when re-importing the product file, you'll need to set "Allow Overwrite" to "Yes".

Bad Behavior
Bad Behavior's files are at `/includes/bad-behavior/`. If you wish to update manually go to:

http://bad-behavior.ioerror.us/download/

And download the latest development version. Extract the zip, and upload the contents of `bad-behavior` to `/includes/bad-behavior/` allowing the files to overwrite.

Versions
The current version of Bad Behavior this mod is using is: v2.2.14
The current version of Bad Behavior (development) is: v2.2.14

Changelog
Version 1.0.13, 04/23/2013

• Bad Behavior upgraded to 2.2.14

Version 1.0.12, 12/21/2012 -- Released: 02/05/2013

• Bad Behavior upgraded to 2.2.13
• Added some more ranges to whitelist.ini

Version 1.0.10, 09/09/2012

• Bad Behavior upgraded to 2.2.10

Version 1.0.9, 06/17/2012

• Bad Behavior upgraded to 2.2.7

Version 1.0.8, 06/12/2012

• Bad Behavior upgraded to 2.2.6
• New Setting: EU Cookie

Version 1.0.7, 05/04/2012

• Bad Behavior upgraded to 2.2.3
• Cron/Scheduled Task for automatic log pruning added.

Version 1.0.6, 01/04/2012

• Bad Behavior upgraded to 2.1.15

Version 1.0.5, 05/26/2011

• Added option for bypassing users/members.
• If the visitor is a user, and is in usergroup 5, 6, or 7 (admin/mod/super mod) - Bad Behavior is bypassed.
• Modified bad-behavior core to check for Google Web Preview
  • file edited: /includes/bad-behavior/core.inc.php
• Added a link beside the IP address in the log for WhoIs.

Version 1.0.4, 04/28/2011

• Bad Behavior upgraded to 2.1.13 (fixes search engine block issues)
• Added Paypal/Paypal IPN IP address to the whitelist.
• Added payment gateway file names to the whitelist.

Version 1.0.3, 04/21/2011

• Fix #1: Pruning log doesn't work.
• Fix #3: POST more than two days after GET (added support for BB's javascript)
• Fix #5: Cannot modify header information error (suppressed error in BB's function)
• Implemented #6: Filter per key (new admincp option to list keys not to be shown in log)
• Implemented #9: Show link to member profile (if userid is found in headers, link to profile)

Version 1.0.2, 04/10/2011

• Updated /includes/functions_vb_badbehavior.php to:
  • disable Reverse Proxy if Reverse Proxy Addresses are empty
  • distinguish SQL queries using "SET", for example: SET @@session.wait_timeout = 90 - which is used by BB
  • set "offsite_forms" to false by default, as it's not really needed in vB IMHO, and it can cause problems with certain setups
  • cleaned up the bb2_read_settings() function and fixed a typo in one of the vbulletin options calls
• Updated /includes/whitelist.ini to include the following GOOGLE ranges:
  • 74.125.0.0/16
  • 216.239.32.0/19
  • 209.85.128.0/17
  • 66.102.0.0/20
• Updated /admincp/vb_badbehavior.php
  • Log pruning was pruning all logs, despite what was entered for number of days

Version 1.0.1, 04/06/2011

• Bad Behavior upgraded to 2.1.12
• Changed files:
  • /includes/bad-behavior/core.inc.php
  • /includes/bad-behavior/searchengine.inc.php
• "Verbose" admin option now set to "No" by default.

Version 1.0.0, 04/05/2011

• Initial release.

Screenshots
Screenshots can now be seen at: http://www.secondversion.com/images/vb/vb_badbehavior/

I was running out of room for attachments here on vB.org


Development

https://github.com/ericsizemore/vb_b...ree/master/vb3


Only those who "Mark As Installed" will receive support for this modification.

[Eric]

Reserved for future use.

[error10]

The screenshots look very nice; I'm going to throw this up on a dev box with 4.1 later and see what happens.

By the way, 2.1.11 is quite stable now; it's going to end up being the 2.2 release candidate shortly (I have to fix some stuff in the MediaWiki port first). Then I can get down to the business of squashing some completely new spammers who have been annoying me lately.

[Alfa1]

Thanks Eric. Does the log show only the users / bots that have been blocked? I see valid users in the log. I have just installed this addon a few minutes ago and already have 491 entries.

[error10]

Originally Posted by Alfa1

Thanks Eric. Does the log show only the users / bots that have been blocked? I see valid users in the log. I have just installed this addon a few minutes ago and already have 491 entries.

Hmm. It SHOULD log everything only when verbose mode is enabled in the settings. If it's off, only blocked requests should be logged. Did you enable verbose mode? If so, try disabling it.

[Eric]

If "Verbose" is enabled, it logs everything, but if the code is 00000000, that means they have not been blocked. You may want to set "Verbose" to "No" to only log suspicious requests/bots (including blocks).

EDIT: error10 beat me to it It appears I have "Verbose" defaulted to "Yes", maybe I should change that in the next release.

[error10]

Originally Posted by Eric

EDIT: error10 beat me to it It appears I have "Verbose" defaulted to "Yes", maybe I should change that in the next release.

I default Verbose to No, since most people don't need it. It's only useful if you're gathering data on spammers that Bad Behavior doesn't yet block.

Speaking of which, I just posted my official announcement. I hope you like it.

[Alfa1]

Verbose logging is off. The code is 00000000 for valid users.

As a side note: The Project Honeypot website is not very structured. It took me a while to find where I needed to go here for a BL API key. So here is the url so that others don't have to search: http://www.projecthoneypot.org/httpbl_configure.php
Could be handy to add to the instructions.

[Eric]

Originally Posted by error10

I default Verbose to No, since most people don't need it. It's only useful if you're gathering data on spammers that Bad Behavior doesn't yet block.

Speaking of which, I just posted my official announcement. I hope you like it.

Yeah, I'll default it to "No" or "Off" in the next release.

And, awesome! Thanks for the blog post, and well.. Bad Behavior itself I have this modification implemented on a forum with nearly 200,000 members, and millions of pageviews/mo - and it's working flawlessly. After 24 hours of use: "There are 3,441 total log entries." (that's not counting the 00000000 entries)

[Eric]

Originally Posted by Alfa1

Verbose logging is off. The code is 00000000 for valid users.

As a side note: The Project Honeypot website is not very structured. It took me a while to find where I needed to go here for a BL API key. So here is the url so that others don't have to search: http://www.projecthoneypot.org/httpbl_configure.php
Could be handy to add to the instructions.

If those requests are still being logged, it could be the type of request the user is making, but that code indicates they are not being blocked.

EDIT: Thank you for the more direct link for http:BL - I'll be sure to include that.