Hi Henning,
If I understand correctly, the blacklisting is done at URI level (which
URI?) and not at IP level, right?
Regards,
Bogdan
Henning Westerholt wrote:
On Wednesday 27 February 2008, Iñaki Baz Castillo
wrote:
El Wednesday 27 February 2008 10:41:45 Henning
Westerholt escribió:
An additional functionality that this module
provides is the ability to
handle global blacklists. This lists are loaded on startup into memory,
thus providing a better performance then in the userblacklist case.
Hi, what is the difference between these "global blacklists" and
the
already existing blacklists (by using "dst_blacklist" and
"use_blacklist")?
Maybe the use of a database to store the IP's?
Hi Iñaki,
the core blacklists work on IP level, as you mentioned. This modules allows to
blacklists certain number prefixes per user or on a global level. Perhaps is
should add this bit of informations to the docs.. ;-)
As a suggestion, shouldn't all this blacklist
stuff (new module and
existing core feature) be merged in just a module (maybe called
"blacklists")?
Well, i don't know if its possible (or feasible) to move the autoblacklist
feature from the core into a module, as this is probably more a low-level
functionality.
Cheers,
Henning
_______________________________________________
Users mailing list
Users(a)lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users