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

[TMM-TT]

Originally Posted by Leo Brazil

I've been using this without any problems but it seems one of our biggest internet providers got blacklisted. So far I don't care, they are big enough to take care of them selves but several members (different IPs) using this provider got affected by this mod.

All those member in fact are not using proxies and you can track their IPs to host names.

Question is how to include this host in Non-block list ?

Example: all users with this problem the host name are like 255-55-55-00.host.name.net

As many IPs have been used I just tried to include host.name.net on the list but it doesn't work.

Any tips ?

That will be included in next version.

[Leo Brazil]

Thanks TMM-TT,

Is there a change to give an option as well to include specific IPs and user IDs ?
I tell you what, specific IPs because sometimes you don't want to alloy the whole host and user IDs, I mean once user was already registered why block them ? Many users are traveling aroung and Hotels or paid internet access use proxies but if the user has logged in it means it's a trully member right ?
Other suggestion is not block instantly visitors and users, in fact I think it should have a option to not block visitors at all only step up in monitoring them as soon they got registered because lots of searching bots use proxies or somenthing like that and could be blocked, and as soon a member is registered just give a warning at moderation panel so moderators can take a look at it and approve a member or not. Using this version it showed very effective in blocking proxies listed as spammers but it was blocking a lot of people that was in fact good faith visitors.

I'll wait for next version.

Sorry for a lot of comments, I only do that when I think a good has a real potential and that's the case here.

[drupy]

Installed.

Do you think it will have any conflict with Proxy IP to Real IP Conversion
by Paul Marsden below?
https://vborg.vbsupport.ru/showthread.php?t=201211

I installed both mods and I was wondering how your mod will work if the proxy IP is converted to real IP by Paul's mod.

Thank you!

[Arboristsite]

Since AOL uses proxies are they effected with this mod?

[AWJunkies]

Originally Posted by Arboristsite

Since AOL uses proxies are they effected with this mod?

I have same question

[Leo Brazil]

Guys, it'll only blocks proxies if the IPs are listed on some black lists websites as spammers and something like that. (you acn even select in your AdminCP what black lists and sites you want to check to confirm an IP)
Even using a proxy if it's not listed as spammer, this one will pass through as normal.

[AWJunkies]

Ok thanks testing it out.

[HaZe_X]

How come I cant get this to work for me?

I have everything enabled, and when I use a proxy site I am still able to view my site

Ex..hidemyass.com

[mjolner]

Is there any way to add the 'include list' to the 'on registration' hook?

      foreach ($proxyinclusions as $inclusionkey => $inclusion)
        {
            if (preg_match("[$inclusion]", $OPMremote) AND $inclusion != "") {$OPMinclude = true;}
        }

(That one)

If you have "only ban on new registration" it doesnt seem to use the Include/exclude list

[basil2070]

Originally Posted by HaZe_X

How come I cant get this to work for me?

I have everything enabled, and when I use a proxy site I am still able to view my site

Ex..hidemyass.com

Have the same problem. Any help?