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]

I think they're may be a conflict with this mod and Google's new PageSpeed service, which we've just started to use....

We keep getting lots of members complaining of timeouts (blocking?) when they attempt to access our site, which is I believe when Google's caching severs attempt to redirect users to our site. There are hundreds of whois "f1182195" entries in our logs.

They all originate from Google's PageSpeed caching servers with IP addresses in this range 173.194.xx.xx.

GET /showthread.php?t=24952&p=137388 HTTP/1.1
Accept: */*
From: googlebot(at)googlebot.com
Connection: Keep-Alive
User-Agent: Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)
X-Pss-Loop: pagespeed_proxy
Accept-Encoding: gzip
Host: www.xxxx.com
Cache-Control: no-cache
X-Forwarded-For: 66.249.74.150

Note: I put the xxx's in the above quote for privacy.

How can I address this, short of turning OFF and not using Bad Behavior? Can I whitelist the range of server IP's and what would be the correct line to add to the whitelist.ini file?

Thanks for any help...

Regards,
Doug

f1182195 key = HTTP Response: 403
Explanation: An invalid request was received. You claimed to be a major search engine, but you do not appear to actually be a major search engine.
Log Message: User-Agent claimed to be Googlebot, claim appears to be false.

[BadgerDog]

Can some explain to me what this entry in whitelist.ini will allow and not allow as far as IP addresses, to access our site?

I'm trying to understand the .0.0 meaning... does that act as a wildcard so any number in there makes that a vaild entry to be able to access our site?

Thanks..

Regards,'Doug


; Extra GOOGLE ranges
ip[] = "74.125.0.0/99"
ip[] = "216.239.32.0/19"
ip[] = "209.85.128.0/17"
ip[] = "66.102.0.0/20"

[TheSupportForum]

Originally Posted by BadgerDog

Can some explain to me what this entry in whitelist.ini will allow and not allow as far as IP addresses, to access our site?

I'm trying to understand the .0.0 meaning... does that act as a wildcard so any number in there makes that a vaild entry to be able to access our site?

Thanks..

Regards,'Doug


; Extra GOOGLE ranges
ip[] = "74.125.0.0/99"
ip[] = "216.239.32.0/19"
ip[] = "209.85.128.0/17"
ip[] = "66.102.0.0/20"

the developer hasnt updated them, there are about 3 more ranges
he needs to use, which i put into the whitelist.ini myself

[TheSupportForum]

current issues with 1.0.10
the following varnames are not set as integer

vb_badbehavior_httpbl_threat
vb_badbehavior_httpbl_maxage

[vb50kgpoo]

Keen to download and impliment this as soon as the latest version is available. Just removed another product that was treating GoogleBots as a log referer spammers, and the log file it generated on log file spammers was viewable publicily, so this other mod was actually causing log referer spammers to target my site!!

So please hurry and release the new version Eric

[Videx]

Last month we started getting lots of 403 errors from Google. I can't say I've done a lot of research, but the only thing I remember changing last month was updating this mod (Oct. 19 judging from my posts).

A quick web search pointed to earlier versions of BB causing this, so Saturday evening I disabled this mod and will be keeping an eye on Google webmaster tools to see if the error continues.

[TheSupportForum]

Originally Posted by Videx

Last month we started getting lots of 403 errors from Google. I can't say I've done a lot of research, but the only thing I remember changing last month was updating this mod (Oct. 19 judging from my posts).

A quick web search pointed to earlier versions of BB causing this, so Saturday evening I disabled this mod and will be keeping an eye on Google webmaster tools to see if the error continues.

thats what i told they guy too but hes not bother about that, googlebot can activity crawl a website unless you change the settings in google webmater tools, the other day i limited to about 5 visits

[vb50kgpoo]

Originally Posted by TheSupportForum

thats what i told they guy too but hes not bother about that, googlebot can activity crawl a website unless you change the settings in google webmater tools, the other day i limited to about 5 visits

Oh dear, and I was so hopefuly this mod would be good, as I had to remove another product for labelling Googlebot as a referer spammer and creating a referal spam hole in my site.

[TheSupportForum]

Originally Posted by vb50kgpoo

Oh dear, and I was so hopefuly this mod would be good, as I had to remove another product for labelling Googlebot as a referer spammer and creating a referal spam hole in my site.

ok well you still dont understand then this product, and my product both use the projecthoneypot API so if its more than 1 product identifiying the same issue

then my guess as i said before it projectshoneypot not our mods

[Videx]

I too installed a honeypot way back when I first installed this mod. But I haven't done anything to change it since. So unless last month's BB update affected it, I'm not sure I can blame the honeypot. But I guess I'm going to have to look up the uninstallation instructions just in case.

edit: Turning off Honey Pot was as simple as going to the dashboard on their site and clicking the link. I also deleted the one html page in my html root that I had put there for them. However, it was not the page giving me 403 errors.

I also checked Google Webmaster tools and there was only a single bad gateway error listed since I turned off BB Saturday. No 403 errors.