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.

[Alfa1]

I look forward to the next version as well. It will resolve the issue of 80 legitimate members being blocked every day.

[raj4x]

Hi Eric,

Looks awesome.

Forgive my ignorance but how does vB Bad Behavior differ from Spam-O-Matic?

Cheers, Raj.

[Lee G]

From memory spam o matic works by connecting to different databases and checking ip when people hit the register button

This works even further up the line

It checks user agents, connection methods and the person gets an error page
Along with checking the ips against project honey pot
Using this, they spammers / scrapers / email harvesters dont even get a look at any pages, let alone being able to hit the register button

Its worth running the two side by side. I run the original stop forum spam from on here, along side this. I get very few spam registrations these days

I also found on my forums that htaccess user agent bans were not working
But by putting the same user agents into the blacklist file on the bad behavior mod, I can get around the problem. By adding all the search engines that are genuine to the whitelist file, you dont inadvertently block the likes of Google etc

One of the first things you notice is the lack of spam hitting your email each day

[Eric]

Still working on 1.0.5. I never heard back from error10, so I modified a core bad-behavior file myself for the Google Web Preview issue. I'm estimating a release sometime in June.

Currently:

Version 1.0.5, 06/??/2011
- Added option for bypassing users/members.
	o 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
	o file edited: /includes/bad-behavior/core.inc.php
- Added a link beside the IP address in the log for WhoIs.

Code Changes: http://trac.assembla.com/vb-bad-beha...%40trunk%2Fvb3

[Alfa1]

Could you please push out a small release inbetween, so that my members are no longer blocked by BB?

[BirdOPrey5]

Originally Posted by Eric

Still working on 1.0.5. I never heard back from error10, so I modified a core bad-behavior file myself for the Google Web Preview issue. I'm estimating a release sometime in June.

Currently:

Version 1.0.5, 06/??/2011
- Added option for bypassing users/members.
	o 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
	o file edited: /includes/bad-behavior/core.inc.php
- Added a link beside the IP address in the log for WhoIs.

Code Changes: http://trac.assembla.com/vb-bad-beha...%40trunk%2Fvb3

Not installed yet but following closely. For the usergroup bypass- will this be an option in the settings or will 5, 6, and 7 be hard coded? I hope I can enter additional usergroups to bypass in the settings- both primary and secondary.

Thanks.

[Eric]

Originally Posted by Alfa1

Could you please push out a small release inbetween, so that my members are no longer blocked by BB?

I will try to get 1.0.5 out as soon as possible. I am rather busy right now, just started my first two college courses on Monday

Originally Posted by BirdOPrey5

Not installed yet but following closely. For the usergroup bypass- will this be an option in the settings or will 5, 6, and 7 be hard coded? I hope I can enter additional usergroups to bypass in the settings- both primary and secondary.

Thanks.

5, 6, 7 will be hard coded but you will also be able to enter additional usergroups

[Lee G]

Thanks for the update Eric
Good luck with the studies

[Eric]

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.
• Changes: http://trac.assembla.com/vb-bad-beha...%40trunk%2Fvb3

[Lee G]

Cheers for that Eric, top man

Made similar changes to those posted by BadgerDog on the VB4 version, for my registered member groups
https://vborg.vbsupport.ru/showpost....8&postcount=48