Add-On Releases - DNSBL, RBL - Open Proxy monitoring/blocking

History

I've had some problems with abuse via open proxies for a time ago, and when we were banning abusers, they always found a new proxy to use and register new accounts with. Since this forum was a large type we could'nt just ban e-mails etc just like that, because this was leading to a very large amount of other banned users too.

At IRC, in the other hand, we had Open Proxy Monitors, that was banning everything that was blacklisted in some DNSBL-databases. No spammers had a chance to get in there as long they were listed in such database.

This is a plugin that blocks blacklisted hosts from some different DNSBL's. It uses the global_start-hook, a very simple handler for blocking proxies, and a vBphrase called OPM_Deny.


April 2006

The source has been rewritten a bit. The proxychecker is now using a cache that, by default, stores all ip's in a database for 6 hours. It scans some DNSBL's and can be configured to block proxies from bitmasks (defined in the plugin) which makes it a little bit more reliable, because it does'nt block everything it see).

Configuration is made from the plugin (hopefully there will be a nice admin interface in the future). Exceptions (ip's that can pass through this system even if it is a proxy) are also handled differently now.

// CHANGES
//
// 2008-09-20 (2.0.8)
//
// * Changed the routines for how to handle inclusion/exclusions
// * Splitted up plugins for 3.5/3.6 and 3.7
//
// 2007-08-05
//
// * Fixed reported bug, based on resolved hosts ending with 127
// * Changed database-tables to get rid of (hopefully) duplicate keys
// * Added resolver-function
// * Added two new block-methods available at the efnet-rbl
//
// 2006-06-28 (2.0.6/Another fix)
//
// * Proxyinclusions/exclusions didn't work properly
//
// 2006-06-28 (2.0.5/Fix only)
//
// * Fixed a bug in the $block-array that affected some of the blocking results
//
// 2006-06-28 (2.0.4)
//
// * opm.tornevall.org has a new entry for anonymizers, added support for this
// * Default value on "block everything detected" in plugin changed to "no"
//
// 2006-06-26 (2.0.3)
//
// * Created options for admincp (removed plugin-configuration)
// * Fixed a bit-bug for njabl
// * Plugin is now a function (rbl_livecheck) for external lookups
// * Added options for "only block on newuser-registrations"
//
// 2006-06-22 (2.0.3 RC)
//
// * The monitor is now a function
// * Added small compatibility with other plugins (with return)
//
// 2006-05-13
//
// * sorbs zones added (no bitmasking)
// * opm.blitzed.org removed
// * time() changed to TIMENOW
//
// 2006-04-21
// ==========
//
// * proxyinclusions
// quickly add own hosts that should be treated as a proxy
//


How does it work with other vBulletins?

This filter actually works with both 3.5 and 3.6, but for now, they will be separate versions, but for 3.5 and 3.6 you should look here and for 3.7 you should look here.


How to use the compatibility thing

If you have a plugin that you want to use together with the proxy monitor (only returns a value if a an ip-address is registered as a proxy or not) you can call the function rbl_livecheck like this (example):

PHP Code:

global $rblInstalled;

if ($rblInstalled) {
$remoteIsProxy = rbl_livecheck(1, $_SERVER['REMOTE_ADDR']);

//
// .. your code here ..
//

} 


Report bugs if you find them...



Don't forget to install it

[terminator2k2]

I'm still using vb 3.7.6 but i will update to 3.8.2 in a month

can this one be used under 3.7 or should i use this (https://vborg.vbsupport.ru/showthread.php?t=191398 ) ?

[Deimos]

Getting a whole bunch of MysqL errors after installing this

Database error in vBulletin 3.8.2:

Invalid SQL:
INSERT INTO proxycache (ip, listed, dateline) VALUES ('xx.xx.xxx.xxx', 0, 1239258676);

[steampunks]

What if I don't wish to block?

Instead I prefer to receive an automated PM (as with the cookie detector mod) about which member is using a proxy.

If a proxy is always blocked regardless, the troll will just move on to another proxy method and the moderation team is none the wiser that a troll is on the prowl.

[ouch]

This works great if the proxies are blacklisted, but if i add some proxies to be treated as such it fails badly...for instance here's a small example that bypass this,

http://www.yourhideway.info/

Now im supposed to be able to include that for monitoring ie 'List of hosts, separated with ENTER, that should be considered as proxies'.

FAILED

[Playa82]

sorry, but it doesn't work. i tried 9-10 proxys. none of them where blocked... :-(

[peterle1]

How can I use this with zen.spamhaus.org?
I use spamhaus with our mail servers and have some good experiences with it.

Inserting zen.spamhaus.org doesn't seem to work and spammers still got through, even if they are listed at spamhaus.

Thanks for any help.

[peterle1]

This does not work for me and I would like to test why, but don't know how to do this.
Anyone with any hints here?
Thanks!

[Wizardjv]

I have a simple question. When entering domains into the allow and block list via admincp. What is the format that they are supposed to be entered in to block and allow them? I think maybe thats where people are having problems. Does anyone have this working? If not I guess it just doesnt work

[dutchbb]

After installing, a lot of legit members got banned, so I uninstalled it. NOt very good if you ask me.

[TMM-TT]

Originally Posted by dutchbb

After installing, a lot of legit members got banned, so I uninstalled it. NOt very good if you ask me.

Well, the script is quite adaptable, so you can change the sensitivity via admincp. The default settings is the most optimal to use, but you can also lower the triggers.