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.

[vb50kgpoo]

Originally Posted by TheSupportForum

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

Sorry, your English and rational both are very poor, can you restate your text please?

[TheSupportForum]

Originally Posted by vb50kgpoo

Sorry, your English and rational both are very poor, can you restate your text please?

sorry i will simplify

both this product and mine use projecthoneypot and you said it basically reports the same as mine, so as a suggestion you will need to contact projecthoneypot
with the IP's from the bots so they can investigate it for you


more than likely both our mods report the same thing because its designed to do that
google webmaster tools suggests that it has not issues crawling and no errors visiting

[vb50kgpoo]

Originally Posted by TheSupportForum

sorry i will simplify

both this product and mine use projecthoneypot and you said it basically reports the same as mine, so as a suggestion you will need to contact projecthoneypot
with the IP's from the bots so they can investigate it for you


more than likely both our mods report the same thing because its designed to do that
google webmaster tools suggests that it has not issues crawling and no errors visiting

Eh, no, that is not what I said. That is what you summized and wrongly reported. Your product wrongly labels GoogleBot as a link referer spammer when project honeypot says nothing of the sort; project honeypot says the bot is Google, nothing more, so why would I want to contact them? Anyway, it is mute, as your product has multiple flaws, including the fact the report file is targetting by link referer spammers (your report file is publicly viewable and therefore when it reports the actions of a spammer, it thereby gives the spammer a file / link back to exploit) and I have now uninstalled it.

I have reinstalled Ban Spider by UserAgent which is excellent, and I am waiting for this Bad Behavior mod to be updated so I can also install it.

[BadgerDog]

Originally Posted by Videx

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.

I'm not sure, but I think this mod may be getting in the way of Google services as well....

We operate Google's PageSpeed Service and we've been seeing a LOT of errors...

Maybe it's something else, but I've turned OFF this mod for now until someone can validate it's working correctly.

We were one of the original PayPal donators to thank the developer for the project ..

Regards,
Doug

[vb50kgpoo]

Originally Posted by BadgerDog

I'm not sure, but I think this mod may be getting in the way of Google services as well....

We operate Google's PageSpeed Service and we've been seeing a LOT of errors...

Maybe it's something else, but I've turned OFF this mod for now until someone can validate it's working correctly.

We were one of the original PayPal donators to thank the developer for the project ..

Regards,
Doug

Dang!

I wish someone would produce a bad behaviour mod that has a bot (by name) whitelist, where anything in the whitelist is given a reverse dns lookup to verify they are whom they say. Because it seems this is a common enough problem, and the last bot I want to block is GoogleBot.

[Videx]

Update: We have now risen back where we belong on a Google search - well, almost - we're #2 behind Wikipedia. We had fallen all the way back several pages.

I noticed another oddity. When I went to Webmaster Tools last Saturday it only showed my site as "Shannondale.org", so I added "www.Shannondale.org". I always thought they were basically the same, but this morning I see my vb sitemap is only showing as having been submitted to "www.Shannondale.org". Does Google really expect two sitemaps and can vb even do that?

[vb50kgpoo]

Originally Posted by Videx

Update: We have now risen back where we belong on a Google search - well, almost - we're #2 behind Wikipedia. We had fallen all the way back several pages.

I noticed another oddity. When I went to Webmaster Tools last Saturday it only showed my site as "Shannondale.org", so I added "www.Shannondale.org". I always thought they were basically the same, but this morning I see my vb sitemap is only showing as having been submitted to "www.Shannondale.org". Does Google really expect two sitemaps and can vb even do that?

You want to avoid this, it can affect your rankings. Recommend you use htaccess to cover all bases (.domain-name.com, IP Address - resolve them both to www.domain-name.com).

[Naijasite]

am unstallingg. i use the default setting ....all guest are unable to view the forum,

see the error message

Error 403

We're sorry, but we could not fulfill your request for / on this server.

You do not have permission to access this server. Before trying again, run anti-virus and anti-spyware software and remove any viruses and spyware from your computer.

Your technical support key is: 5bc8-9c4f-2b02-1b1f

You can use this key to fix this problem yourself.

If you are unable to fix the problem yourself, please contact help(@)naiji(.)com and be sure to provide the technical support key shown above.

[Alfa1]

Do not be fooled by the massive number of fake Google bots that are around these days. If the IP/CIDR does not reveal a Google bot then its fake.

Add the following to your whitelist.ini to unblock Google, Baidu Japan and Facebook:

; Extra GOOGLE ranges
ip[] = "66.102.0.0/20"
ip[] = "173.194.0.0/16"
; Extra Baidu ranges
ip[] = "180.76.0.0/19"
ip[] = "119.63.196.0/19"
; Extra Facebook ranges
ip[] = "69.171.224.0/19"
ip[] = "173.252.64.0/18"
ip[] = "66.220.144.0/20"

Please be so kind to include the above into the next release.
The above CIDR ranges come from checking the whois on all bots that visited my big board while I had BB turned off for testing. The above IP ranges belong to valid spiders which are blocked if this is not added to the whitelist.

Does BB whitelist the IPs of pingdom?
https://www.pingdom.com/rss/probe_servers.xml
Pingdom should be whitelisted

[vb50kgpoo]

Originally Posted by Alfa1

Do not be fooled by the massive number of fake Google bots that are around these days. If the IP/CIDR does not reveal a Google bot then its fake.

Add the following to your whitelist.ini to unblock Google, Baidu Japan and Facebook:

; Extra GOOGLE ranges
ip[] = "66.102.0.0/20"
ip[] = "173.194.0.0/16"
; Extra Baidu ranges
ip[] = "180.76.0.0/19"
ip[] = "119.63.196.0/19"
; Extra Facebook ranges
ip[] = "69.171.224.0/19"
ip[] = "173.252.64.0/18"
ip[] = "66.220.144.0/20"

Please be so kind to include the above into the next release.
The above CIDR ranges come from checking the whois on all bots that visited my big board while I had BB turned off for testing. The above IP ranges belong to valid spiders which are blocked if this is not added to the whitelist.

Does BB whitelist the IPs of pingdom?
https://www.pingdom.com/rss/probe_servers.xml
Pingdom should be whitelisted

The trouble is, you do not know whether something is a true GoogeBot or not as Google do not publish all of their IP ranges for obvious reasons. The only safeguard is to do a reverse dns lookup.