PeerGuardian and MoBlock Debian packages / News: Recent posts

There´s a new project: PeerGuardian Linux (pgl), located at the project of the original PeerGuardian: http://sourceforge.net/projects/peerguardian/.

The new project combines and succeeds all projects that had packages here at http://moblock-deb.sourceforge.net. There´s the daemon pgld (based on NFBlock, which was based on MoBlock), pglcmd (based on blockcontrol, previously moblock-control) and pgl-gui (by the author of mobloquer).... read more

Added a watchdog, that restarts blockcontrol if it detects problems. Added support for multiple custom iptables scripts.

I decided to make a PPA at launchpad.net. This means I upload the source packages, and the binaries are then built for the architectures i386, amd64 and (new) lpia. This will be used for Ubuntu jaunty and later versions. The launchpad packages are signed with another gpg key: 9C0042C8

The apt sources.list entries are:
deb http://ppa.launchpad.net/jre-phoenix/ppa/ubuntu jaunty main
deb-src http://ppa.launchpad.net/jre-phoenix/ppa/ubuntu jaunty main... read more

All packages updated.

moblock-control has been renamed to blockcontrol. Have a look at blockcontrol's NEWS: http://moblock-deb.svn.sourceforge.net/viewvc/moblock-deb/blockcontrol/blockcontrol/docs/NEWS.

NFBlock added to the repoitory.

New handling of blocklists:
- php redirects are supported now. This allows to use the lists from iblocklist.com. All lists are downloaded from there per default now.
- Since moblock-control 1.1 the default blocklists are by "The Blocklist Group" (tbg.iblocklist.com) instead of Bluetack (bluetack.co.uk).
- The single blocklists are saved in new places now (but still under /var/spool/moblock/.
- The master blocklist (e.g. guarding.p2p) is now saved in /var/lib/moblock/ instead of /etc/moblock/.
- Several changes to make sure that the master blocklist exists and reflects the configuration. All changes are always applied on "start" now.
- The (Debian) installation only requires the blocklists (and therefore network access) to be available, if the automatic start (init) is configured.... read more

All packages have been updated.

Added support for Ubuntu Intrepid Ibex.

moblock-control is a separate package now
So install "moblock" and "moblock-control" to have the functionality of the old "moblock" package.
The custom iptables scripts now are executed per default, too.
See the moblock-control NEWS (http://moblock-deb.svn.sourceforge.net/viewvc/moblock-deb/moblock-control/moblock-control/docs/NEWS) and changelog (http://moblock-deb.svn.sourceforge.net/viewvc/moblock-deb/moblock-control/moblock-control/debian/changelog)

Since the 0.9 series has less bugs and nicer features then the "official" stable 0.8 I removed the "moblock-nfq" package. Updates to "moblock" will be made automatically. Since the case for "moblock-ipq" is a bit complicated this case is not handled automatically. Interested users with old kernel (<2.6.13) please ask for help for transition.
For the other changes see the MoBlock 0.9RC2 debian changelog: http://moblock-deb.svn.sourceforge.net/viewvc/moblock-deb/moblock/moblock-0.9~rc2/moblock-0.9~rc2/debian/changelog
The subversion development repository is updated again!

debconf support added, port 80 and 443 whitelisted per default again, LAN traffic automatically whitelisted (experimental), port logging, hopefully removed all bashisms - Have fun.

I have not made a separate file release of moblock-control, yet. Contact me if you want one now.

The development repository is still not updated.

Preview packages
You can download preview packages of MoBlock (0.9~rc2-12) here: http://moblock-deb.sourceforge.net/preview
Next to many other changes this version has debconf support. Of course I want to know if it works technically. But I'm also interested in feedback about the debconf descriptions. Are they unclear, too technical, ...?

Development repository currently not updated
The version control software that I use (svk) is currently not in Debian lenny, therefore I don't sync my local changes to the development repository.

Repository redesigned, amd64 packages added:

Yay, now I can build amd64 packages natively and test them myself. So here you go, get i386 or amd64 packages from moblock-deb.sf.net.

I used this occasion to also make a software change: Now the repository is made with reprepro (http://mirrorer.alioth.debian.org/) instead of debarchiver (http://inguza.com/software/debarchiver/). Therefore the repository now finally has the pool structure (no changes needed on your side). The packages are still built with cowbuilder (http://www.netfort.gr.jp/~dancer/software/cowdancer.html) (i386 is emulated, for Debian Etch and Ubuntu Feisty i386 packages I have to use pbuilder (http://www.netfort.gr.jp/~dancer/software/pbuilder.html)). Because Debian Sid failed to bootstrap I use the Lenny packages there, too. At least currently the dependencies are satisfied on both dists.... read more

New default blocklists.
For the other changes see the MoBlock 0.9RC2 debian changelog: http://moblock-deb.svn.sourceforge.net/viewvc/checkout/moblock-deb/moblock/moblock-0.9~rc2/moblock-0.9~rc2/debian/changelog

This fixes problems with deleted/outdated config files.
See the MoBlock 0.9RC2 debian changelog: http://moblock-deb.svn.sourceforge.net/viewvc/checkout/moblock-deb/moblock/moblock-0.9~rc2/moblock-0.9~rc2/debian/changelog

In 0.9~rc2-7 there are only Debian specific changes. So moblock-control stays at the shortly before released version 0.9~rc2-6 which also deals with deleted/outdated config files.... read more

MoBlock 0.9RC2 debian changelog: http://moblock-deb.svn.sourceforge.net/viewvc/checkout/moblock-deb/moblock/moblock-0.9~rc2/moblock-0.9~rc2/debian/changelog

Today, updated mobloquer packages (0.4.1)
some bugfixes.

Already some days ago:

• updated moblock packages (0.9~rc2-3)
  Changelog: http://moblock-deb.svn.sourceforge.net/viewvc/moblock-deb/moblock/moblock-0.9~rc2/moblock-0.9~rc2/debian/changelog?view=log

• moblock-control as sourceforge file release
  You can now download moblock-control (nearly everything in the Debian packages that is not the MoBlock daemon itself) seperately from the project's page. moblock-control is (should be) distribution independent, feedback welcome.

... because they seem not to work. Now I'm trying to setup qemubuilder. No ETA, sorry. Just compile your own packages for the time being.

Now I know that moblock-control does not work with dash, sorry Ubuntu Gutsy users. This version always uses bash now again.

amd64 repository added (except Ubuntu hardy, sorry). Since a few days I also provide amd64 packages (cross-compiled on my i386). Thanks to all those who provided amd64 packages in the past.

New packages (MoBlock 0.9~rc2-1)
The range merge bug (https://sourceforge.net/tracker/index.php?func=detail&aid=1818886&group_id=162910&atid=825649) was fixed upstream. So per default multiple blocklists from bluetack.co.uk in peerguardian .p2p text format are used again. Warning, this is another blocklist format, so accept the changes in blocklists.list and moblock.conf on update!
MoBlock 0.9RC2 debian changelog: http://moblock-deb.svn.sourceforge.net/viewvc/moblock-deb/moblock/moblock-0.9~rc2/moblock-0.9~rc2/debian/changelog?view=log

Fixed "MoBlock does not start after update/install with aptitude" bug.
MoBlock 0.8 Debian changelog: http://moblock-deb.svn.sourceforge.net/viewvc/moblock-deb/moblock/moblock-0.8/moblock-0.8/debian/changelog?view=log
MoBlock 0.9RC1 Debian changelog: http://moblock-deb.svn.sourceforge.net/viewvc/moblock-deb/moblock/moblock-0.9~rc1/moblock-0.9~rc1/debian/changelog?view=log
mobloquer 0.3 Debian changelog: http://moblock-deb.svn.sourceforge.net/viewvc/moblock-deb/mobloquer/mobloquer-0.3/mobloquer-0.3/debian/changelog?view=log

new package: mobloquer, the new GUI for MoBlock by JimTB. With Moblock 0.9rc1 it doesn't show the logging yet, otherwise it's very promising.
New MoBlock package (0.9~rc1-5).
Somehow Moblock doesn't run after the update here, see BUGS: http://moblock-deb.svn.sourceforge.net/viewvc/moblock-deb/moblock/moblock-0.9~rc1/moblock-0.9~rc1/debian/BUGS?view=markup. After restarting it everything works wonderful.
Please have a look at the Debian package changelog to get a complete list of the changes: http://moblock-deb.svn.sourceforge.net/viewvc/moblock-deb/moblock/moblock-0.9~rc1/moblock-0.9~rc1/debian/changelog?view=markup

I've started to package MoBlock 0.9 (Release Candidate 1). So here it is moblock (0.9~rc1-1), use it only if you really want to test it. I've renamed the nfq package and skipped the ipq version.
This version now allows to MARK packets instead of DROPping or ACCEPTing them.
I've also added a /etc/moblock/moblock.default configuration file to make future updates easier.
Warning: This version also logs accepted packages, so your logfile will grow faster than usual.... read more

All problems on install/update should be removed now again. What a painful weekend.

Debian package changelog: http://moblock-deb.svn.sourceforge.net/viewvc/moblock-deb/moblock/moblock-0.8/moblock-0.8/debian/changelog?view=markup

Reverted behaviour of port whitelisting, sorry, I broke this in 0.8-33 :-/

Only one default list (nipfilter.dat from bluetack containing most of the old default lists) because of bug 1818886. Changed configuration variables because of simplified whitelisting.

For all the other changes have a look at the Debian package changelog: http://moblock-deb.svn.sourceforge.net/viewvc/moblock-deb/moblock/moblock-0.8/moblock-0.8/debian/changelog?view=markup

There's a bug in MoBlock: When you use multiple lists and ranges have to be merged then IPs which are higher than the first merged range aren't blocked. See here: https://sourceforge.net/tracker/index.php?func=detail&aid=1818886&group_id=162910&atid=825649

Workaround: use only one list.
Warning: if you use a list in ipfilter.dat format then you have to change the option how MoBlock loads this.... read more

Finally including gutsy versions again.

Just a reminder: Users with kernel 2.6.23 should have a look at https://developer.berlios.de/bugs/?func=detailbug&bug_id=12156&group_id=2509. The patch from there is already applied.