This is a security warning for the current release MoBlock 0.8.
The bug has been solved already in the cvs source (0.9 rc2 and later) at moblock.berlios.de.
E.g. the Debian packages from moblock-deb.sourceforge.net are based on the cvs source, and so are not affected by this bug.

---

Just to keep you informed. Baseline: No need to panic but in some cases MoBlock won't block all IPs that it should:
When you use multiple lists and ranges have to be merged then IPs which are higher than the first merged range aren't blocked. With other words: you should not "cat" together several lists (e.g. those from bluetack in .p2p format). This was the case in the Debian packages up to 0.8-32.

Workaround: use a clean list. In the current debian packages I do so by using bluetack's nipfilter.dat.gz together with the moblock option "-d" for lists in the ipfilter.dat format. (You can download this list from www.bluetack.co.uk/config/[blocklistname] - but I don't want to write a clickable link here).

Warning: if you use a list in ipfilter.dat instead of lists in .p2p format then you have to change the option how MoBlock loads this.
ipfilter.dat: option "-d"
.p2p: option "-p"
You can not use both blocklist formats at the same time!

See here for the history of the bug:
https://sourceforge.net/tracker/inde...10&atid=825649
(The user ebutera in that thread is the upstream author. He's working on solving the bug.)

greets
jre

__________________
Maintainer of http://moblock-deb.sourceforge.net: MoBlock, mobloquer, blockcontrol and NFBlock Debian packages.
Author of blockcontrol, previously moblock-control.