-----Original Message----- From: Jerry Murdock [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 07, 2001 10:03 AM To: Rick Matthews Cc: Squidguard Mailing List Subject: Re: squidGuard Module for Webmin
> > > The module has to make some assumptions to put some > > > structure around the relatively amorphous > > > squidguard.conf file. > > > > Why not start with the squidGuard configuration documentation > > <http://www.squidguard.org/config/>? > > > There is nothing the module does that is outside the docs. I configured my squidGuard using the documentation and squidGuard was fully operational, performing as advertised. I wanted to try the squidGuard Webmin module, so I followed the written instructions and installed and configured the module. The module told me the blacklists were not installed. The module has created limitations and conventions that do not exist in squidGuard. The module and documentation are also completely silent about those limitations and conventions. > > Not true; did you read my previous posts? (Scroll down and read about > > his blacklist path assumption.) > > > The reason for this is obvious if you've ever automated blacklist > updates. Huh? My blacklist updates are completely automated, and not once did I feel the need to invalidate any portion of the squidGuard documentation. > He could and probably will open it up in the future, but why > waste the time now, when other features (such as support > for users) were still needed. Why write it incorrectly in the first place? If you find these lines in a squidGuard.conf file: -------------------------------------- dbhome /usr/local/squidGuard/db dest porn { domainlist block/blacklists/porn/domains urllist block/blacklists/porn/urls } -------------------------------------- The documentation says you will then find the porn domains file here: </usr/local/squidGuard/db/block/blacklists/porn/domains> And that's where squidGuard looks for it, and all is right with the world. The module was written to look for that porn domains file here, instead: </usr/local/squidGuard/db/blacklists/porn/domains> Are you telling me that it was written this way to allow for automated updates? Or are you saying that he saved time doing this way? Even if both of these statements are true (they're both false), what was gained by not communicating this fact to the user? > > In fact, if you have already set up squidGuard and have it running, I'd > > advise you to stay away from the squidGuard module for Webmin. > > Too much effort to set up, too little return when you've finished. > > > This I can't really understand. It took me, at most, 15 minutes > to install and have running on FreeBSD(which required a minor > modification to the source), 15 minutes to play with, and maybe > another 10 minutes to "webmin-enable" my squidguard.conf. Wow, would you please re-read your comment? Would you say that Squid and its 2,000+ line configuration file is more or less complex than squidGuard? If you already had squid up and running (meaning that you already had a working knowledge of the squid.conf file), what would you write about the effort to install and configure the squid module for Webmin? The squid module took me 1 minute to install and another minute to configure. Period. It might have been worth suffering through a heavy dose of discovery, trial and error to be able to use the squidGuard module, if it shortened the learning curve, simplified configuration or automated significant tasks. But it doesn't do that. Even after squidGuard is up and running, here's a list of the tasks that a squidGuard administrator will face: - Regularly download blacklists (from two or more sites for better porn coverage) - Maintain local list of sites to be added (2 files per category) - Maintain local list of sites to be deleted (2 files per category) - Merge multiple lists, include local_adds, remove local_deletes and dedupe resulting file (without getting your hands crossed and without stepping on the production files) - Create new databases using the -C command - Update the databases from diff files using the -u command - Move new files into production with squid -k reconfigure (or stop/start) - Review squid and squidGuard log files for errors - Occasionally will need to revert to a previous set of files How many of these does the squidGuard module simplify, automate, or even address? I think the answer is zero. Rick
