The master version is at http://info.ost.eltele.no/freeware/squidGuard/faq.shtml
This page was last modified on Wednesday, 28-Jul-1999 13:45:32 MET DST
squidGuard Frequently Asked/Answered Questions (FAQ)
A free filter, redirector and access controller for Squid

Note: this page is primarily written for squidGuard-1.0.x. Though most of it still applies to squidGuard-0.9.x.

Contents

FAQ - Frequently Asked/Answered Questions

Currently in semirandom order:

  1. How can I test timeconstraints
    You can set a simulated start time with the -t yyyy-mm-ddTHH:MM:SS option:
    squidGuard -c test.conf -t 1999-12-31T23:59:30 -d <test.in>test.out 2>test.log
    With the -t option squidGuard parses the given date&time and calculates an offset from the current time at startup and then adds this offset to all timevalues during runtime.

  2. squidGuard compiles fine and the tests succeeds, but it seems to pass all when run under Squid
    There may be at leaste two reasons for this:
    • Some versions of Squid (supposedly 2.2.*) silently ignores argumets to the right of redirect_program prefix/bin/squidGuard. Solutions are one of:
      • Set the actual config file location at compiletime with --with-sg-config
      • Use a shell wraper with redirect_program prefix/bin/squidGuard.sh and make prefix/bin/squidGuard.sh an executable shell like:
        #! /bin/sh -
        exec prefix/bin/squidGuard -c whatever/squidGuard.conf
    • When run under Squid, squidGuard is run with the same user and group ID as Squid (cache_effective_user and cache_effective_group in squid.conf). The squidGuard configuration and database files must be readable for this user and/or group and the squidGuard log directory must be writable for this user and/or group. If not squidGuard will go into the "pass all for all" emergency mode.

  3. compilation of sg.l on fails with "sg.l:line ...: Error: Too many positions" with native lex
    Some native versions of lex have problems with sg.l. The solution is to use GNU flex wich is better anyway. Do "setenv LEX flex" if configure selects the native lex before flex. Flex should compile right out of the box similar to other GNU programs. (Thanks to laurent.foulonneau@mail.loyalty.nc).

  4. Are there any blacklist exchange plans?
    There are no concrete plans currently. We would like to involve in such a project if someone could give us some clever solutions for how to tackle these problems:
    • How can we distribute blacklists without publishing the ultimate Internet guide to banned sites?
      • Should we use a registration scheme?
      • Could a dual key systems like PGP help us here?
      • Is a mailinglist the solution?
    • Spammers could blacklist "microsoft.com". (Fine with me, but I'm sure the average user would complain..). How can we avoid spammers attacks?
    • In some "free" countries suing people seems like a public sport. What happens if we blacklist their fine site?
    • Some URLs would be visually verified as bad content, while others would come from dumb robots. Should they be mixed?
    • At what level should we put the threshold? The opinion on what is acceptable and not differs considerably, not only between different parts of the world but also within a community. Some think bikini/swimsuit pages should be banned others think topless is OK..
    • What copyright should such a list have? Should we help commercial competitors by feeding them with suspect links, or should we put in some "water marks" to catch abuse?
    The sample blacklist included in the source distribution is the current compromise and a regularely updated version is now available in the distribution directory.
    We are planning to include our robot as a contrib in the next public release of squidGuard. A snapshot is available here. There is currently no documentation for the robot.

  5. Can I use proxy authenticated user the same way as RFC931/Ident user?
    If you patch Squid with this simple diff, gently contributed by Antony T Curtis, the authenticated user will be passed from Squid to squidGuard and the answer will be yes, otherwise no:
    	A useful patch to Squid 2.2STABLE which fixes per-user redirection where
    	the user is authenticated using proxy-auth...
    
    	*** src/redirect.c.orig Tue Jun 22 14:04:43 1999
    	--- src/redirect.c      Tue Jun 22 15:46:41 1999
    	***************
    	*** 103,108 ****
    	--- 103,110 ----
    	      cbdataAdd(r, cbdataXfree, 0);
    	      r->orig_url = xstrdup(http->uri);
    	      r->client_addr = conn->log_addr;
    	+     if (http->request->user_ident[0])
    	+       r->client_ident = http->request->user_ident; else
    	      if (conn->ident == NULL || *conn->ident == '\0') {
    		r->client_ident = dash_str;
    	      } else {
           

If you have questions and/or answers that should be on the FAQ list please send them to squidguard@ost.eltele.no

Copyright

squidGuard is covered by the GNU General Public Licence (GPL). The copyright boils down to:

For more copyright details you have to read the GNU General Public Licence (GPL).

Feedback

If you find a bug, have a bug fix, a contribution, a question or a comment on squidGuard feel free to send it to squidguard@ost.eltele.no

The preferred bug fix format is context diff:
diff -c origfile fixedfile
or
diff -cr origdir fixeddir
Please explain what problem your diff fixes.

Success reports are very welcome too.. They makes us even more enthusiastic!

Authors

squidGuard was designed by Pål Baltzersen and implemented by Lars Erik Håland
at ElTele Øst AS and made freely available by permission of ElTele Øst AS.

This page is written and maintained by Pål Baltzersen.
Please report any errors, broken links, missing stuff, typos, misspellings, wrong grammar, norwenglish phrases etc. you discover.