Integration with vBulletin - vB Bad Behavior (vB4)

/**
* 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 vB 4.x, it was tested on 4.1.2/4.1.3. Screenshots are from vB 3.x, but it should still look relatively the same with vB4.

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 -> Settings -> 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.16
The current version of Bad Behavior (development) is: v2.2.16

Changelog
Version 1.0.14, 09/22/2015

• Bad Behavior upgraded to 2.2.16

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/vb4


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

[BadgerDog]

Originally Posted by Alfa1

You can whitelist ie6 if you want, but unless your forum is aimed at government employees, I would not see a reason to do so.

Where (and how) can I whitelist outside un-registered users accessing our site who are using IE6?

Thanks for any guidance ..

Regards,
Doug

[Alfa1]

In whitelist.ini you can add any useragent that you would want to whitelist. The file explains itself, as it already whitelists some user agents.

[evilTone]

i've had to de-activate this until it allows ie6 users to view the site, shame is its a nice modification.
i know i can add ie6 to whitelist but the whitelist says that each useragent needs to be input in full. there are quite a combination so i'll sit this out until its sorted

[BadgerDog]

Is there any possibility that this mod has caused a problem with PayPal, specifically with the following files in 4.1.3.

payments.php and payment_gateway.php

It appears that after 5 years of using PayPal for subscriptions and changing nothing else, that about the time we installed/update this mod, PayPal's return communciations to vBulletin has stopped working. Payments are being accepted and processed by PayPal, but the vBulletin end where it would log the transactions and update user records has stopped working, about a month ago.

Also, we use Skimwords which is built into our vBulletin and it helps with augmenting site revenue. I notice in the Bad Behavior logs that it's blocking "SkimWordsBot/1.0".

Where are the white lists located so we can make sure communications from appropriate sources are being permitted through to our site?

Regards,
Doug

[Alfa1]

whitelist.ini is located in /includes/
You can just add payments.php and payment_gateway.php to the whitelist. And SkimWordsBot as well.

[BadgerDog]

Originally Posted by Alfa1

whitelist.ini is located in /includes/
You can just add payments.php and payment_gateway.php to the whitelist. And SkimWordsBot as well.

Thanks ... :up:

I added payments.php only, as payment_gateway.php was already there ...

I also added SkimWordsBot/1.0 as a useragent ...

I noticed that the IP addresses listed for PayPal, don't seem to correlate to what PayPal is showing on their Go Live Checklist

Should these be changed in the whitelist and is it possible that's been causing the blocking I've been experiencing in the last 30 days?

Regards,
Doug

[Alfa1]

It cant hurt to add these IPs.

[Rik Brown]

How do I know this mod is working on my site?

I've set it up with our http:BL API Key (a bunch of lowercase letters) but I'm not seeing anything changed in my apache log.

I have even enabled verbose logging. Does it log elsewhere? If so, where?

Is there some term I can use to grep my log file with to find instances where the mod has caught a bot?

Thanks. -- Rik

[flyaddict]

Dumb question...where do I find the logs?

[Alfa1]

Admincp > logs