The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
vB Bad Behavior Details »» | ||||||||||||||||||||||||||
/**
* 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
Version 1.0.12, 12/21/2012 -- Released: 02/05/2013
Version 1.0.10, 09/09/2012
Version 1.0.9, 06/17/2012
Version 1.0.8, 06/12/2012
Version 1.0.7, 05/04/2012
Version 1.0.6, 01/04/2012
Version 1.0.5, 05/26/2011
Version 1.0.4, 04/28/2011
Version 1.0.3, 04/21/2011
Version 1.0.2, 04/10/2011
Version 1.0.1, 04/06/2011
Version 1.0.0, 04/05/2011
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. Download Now
Show Your Support
|
Comments |
#112
|
|||
|
|||
I should hope most people will never see it. In any case you can advise your user to click the fix it yourself link and to use the registry cleaner provided. (He will have to reboot the computer after using it, but the page also explains that.)
|
#113
|
||||
|
||||
Great, thanks for that, soooooooo one last question (i guess for Eric) where are these custom pages stored so we can make the message more prominant, add our forums css and maybe add a link to a helpdesk (this is how i was contacted by my user)?
|
#114
|
||||
|
||||
Sounds great but wouldn't that mean storing all useragents & IP's used by each user in the database?, i say this because BB would need to know to allow that user to even view the site in the first place, naturally if the user gets to login they've gone as far as the need to anyway. I'm not sure how you would police it without storing that added information for every user, unless i've misread how BB works.
|
#115
|
|||
|
|||
Hey, let's see if I can learn to multi-quote!
Quote:
Quote:
|
#116
|
||||
|
||||
Again, thanks for the responses, i've tinkered ever so slightly with responses.inc.php to add the url to my helpdesk just before
Quote:
I see that what you're trying to do is commendable and fantastic, you've saved my bandwidth usage no end (when next months revenue comes in i'll make a donation....already did to project honey pot as i thought that was yours, was still a worthy donation), what i do see is that if you did fill the request to have every visitors user agent...etc checked with projecthoneypot, htppBL and every entry in your own database to summise it's a registered user then the server load and resource usage would kill your forum (on a busy one anyway or if you are running VPS or VM's). I believe the way you are tackling it is the most sensible, the honing of this software and minimising the effect on honest organics is definitely the way to go. I guess the only other option for "suspect" real users is to filter those through to another list or moderated usergroup so they can then be contacted through the forum for an organic response this way you would also capture any secondary ip they may be using to allow you to whitelist them, perhaps to this end is it possible to add to your roadmap 3.0 to have the whitelist (and maybe a blacklist) integrated into vBBB so that it can be edited directly in admincp>vb Bad Behaviour Options (probably one for Eric?)? Anyway above all, another great big thanks to you guys, nominated MOTM |
#117
|
|||
|
|||
Thanks for your compliments.
One thing to note: Bad Behavior is not intended to be a complete anti-spam solution; it should not be the only thing you run. Bad Behavior should also not do certain things and indeed, a close inspection of the code will reveal quite a few things which have been either partially implemented, or tested and found to not work and therefore disabled. Bad Behavior is meant to block a majority of obvious spam, in order to reduce server load and reduce the amount of spam messages and registrations to a level that is manageable with more traditional tools. Because this is done by completely blocking the request and stopping vBulletin (or other software) from completing loading, it's simply not possible for me to do everything. Some things must be let through because I can't reliably distinguish them in real time. Bad Behavior is also not meant to be a general purpose blacklisting tool, as a few people here have tried to use it. While it does contain an internal blacklist, these items are limited to well known malicious user-agents which scrape, harvest addresses, deliver spam or execute attacks. Things like ht:track and wget are intentionally not on the blacklist because many people want such software to visit their sites, and they are not designed as malicious tools. It's better to add such things to your local .htaccess (or equivalent) if you intend to block them. Perishable Press has some really good starting points. |
#118
|
|||||
|
|||||
Quote:
Just to make sure, here are some more. All from valid members: Please check out: OpenSearch By far most issues seem to be related to this. Quote:
Quote:
Quote:
Quote:
|
#119
|
||||
|
||||
Quote:
Quote:
|
#120
|
||||
|
||||
Quote:
Quote:
Quote:
|
#121
|
||||
|
||||
Thanks! I assume I can just use html in there?
|
Thread Tools | |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|