
   [1][eto-small.gif] The master version is at
   [2]http://info.ost.eltele.no/freeware/squidGuard/
   This page was last modified on Wednesday, 03-Nov-1999 19:04:47 MET
   
   Welcome to squidGuard [3][squidGuard.gif] 
   An ultrafast and free filter, redirector and access controller for
   Squid
   
   Note1: this page is primarily written for squidGuard-1.0.x. Though
   most of it still applies to squidGuard-0.9.x.
   Note2: To print [4]all-in-one go [5]here.
   Note3: The [6]FAQ is [7]here.
   Note4: The [8]ANNOUNCE message is [9]here.
   
Contents

     * [10]Contents
     * [11]Downloading
     * [12]Introduction
     * [13]Capabilities
     * [14]Portability
     * [15]Installation guide
       
     * [16]For the impatient
     * [17]For the less impatient
       
     [18]Configuration guide
     * [19]The configuration file
       
     * [20]In general
       
     * [21]The Structure
     * [22]Reserved words
     * [23]Declaration names/lables
     * [24]Breaking long lines
       
     [25]Path declarations
   
     [26]Time space declarations
   
     [27]Source group declarations
   
     [28]Destination group declarations
   
     [29]Rewrite rule group declarations
   
     [30]Access Control Lists
   
     [31]The database
     * [32]Domainlists
     * [33]URLlists
     * [34]Expressionlists
       
     [35]Tuning hints
   
     [36]Working configuration examples
     * [37]Example 0 - The absolutely minimal do nothing
     * [38]Example 1 - The recommended minimal do nothing
     * [39]Example 2 - Limiting the access to one destination group only
     * [40]Example 3 - Blocking the access for unknown or unprivileged
       clients
     * [41]Example 4 - Blocking inapropriate sites
     * [42]Example 5 - Blocking inapropriate sites for some users and
       blocking unknown clients
     * [43]Example 6 - Blocking inapropriate sites partially with regex
     * [44]Example 7 - Blocking inapropriate sites during business hours
       only
       
     [45]A glimpse behind the curtain
     * [46]How squidGuard comunicates with Squid
     * [47]How squidGuard decides what to do
     * [48]What makes squidGuard so fast
     * [49]Special notes, features and oddities
     * [50]News and changes
     * [51]Known bugs and misfeatures
     * [52]To do or not to do
       
     [53]FAQ - Frequently Asked/Answered Questions
   
     [54]Links to related documentation
   
     [55]Useful software links
   
     [56]Copyright
   
     [57]Feedback
   
     [58]Authors
   
     [59]Contributors
   
Downloading

   The release directory for squidGuard is accessible by both [60]HTTP
   and [61]FTP
   The current production release is [62]squidGuard-1.1.1
   New: A regularly updated [63]sample blacklist is now also available.
   
   Se the [64]News and changes and [65]Known bugs and misfeatures
   sections for more info on the releases.
   
Introduction

   squidGuard is a combined filter, redirector and access controller
   plugin for [66]Squid. It is
     * [67]free
     * [68]very flexible
     * [69]extremely fast *)
     * [70]easily installed
     * [71]portable
       
   squidGuard can be used to
     * limit the web access for some users to a list of accepted/well
       known web servers and/or URLs only.
     * block access to some listed or blacklisted web servers and/or URLs
       for some users. **)
     * block access to URLs matching a list of regular expressions or
       words for some users. **)
     * enforce the use of domainnames/prohibit the use of IP address in
       URLs. **)
     * redirect blocked URLs to an "intelligent" CGI based info page. **)
     * redirect unregistered user to a registration form.
     * redirect popular downloads like Netscape, MSIE etc. to local
       copies.
     * redirect banners to an empty GIF. **)
     * have different access rules based on time of day, day of the week,
       date etc.
     * have different rules for different user groups.
     * and much more..
       
   Neither squidGuard nor Squid can be used to
     * filter/censor/edit text inside documents
     * filter/censor/edit embeded scripting languages like JavaScript or
       VBscript inside HTML
       
   *) 100,000 requests in 10seconds on a 500MHz Pentium with lists of
            5900 domains
            7880 urls
          13780 total
          
       100,000 requests in 12seconds on a 500MHz Pentium with lists of
              5900 domains
          200000 urls
          205900 total
          
       I.e. domain and URL listsizes has neglectable performance effect..
          
   **) squidGuard is not a porn or banner filter/blocker, but it is very
          well suited for [72]these purposes too.
          
Capabilities

   squidGuard has many powerful [73]configuration options that lets you:
    1. [74]define different time spaces based on any reasonable
       combination of
          + [75]time of day (00:00-08:00 17:00-24:00)
          + [76]day of the week (sa)
          + [77]date (1999-05-13)
          + [78]date range (1999-04-01-1999-04-05)
          + [79]date wildcards (*-01-01 *-05-17 *-12-25)
    2. [80]group sources (users/clients) into distinct categories like
       "managers", "employees", "teachers", "students", "customers",
       "guests" etc. based on any reasonable combination of
          + [81]IP address ranges with
          + prefix notation (172.16.0.0/12)
          + netmask notation (172.16.0.0/255.240.0.0)
          + first-last notation (172.16.0.11-172.16.0.35)
    3. [82]address lists (172.16.134.54 172.16.156.23 ...)
    4. [83]domain lists (foo.bar.com ...) *)
    5. [84]user id lists (weho sdgh dfhj asef ...) **) and optionally
       link the group to a given time space
          + positively (within business-hours)
          + negatively (outside leisure-time)
    6. [85]group destinations (URLs/servers) into distinct categories
       like "local", "customers", "vendors", "banners", "banned" etc.
       based on an unlimited number of unlimited lists of
          + [86]domains, including subdomains (foo.bar.com)
          + [87]hosts (host.foo.bar.com)
          + [88]directory URLs, including subdirectories
            (foo.bar.com/some/dir)
          + [89]file URLs (foo.bar.com/somewhere/file.html)
          + [90]regular expressions ((expr1|expr2|...))
       and optionally link the group to a given time space:
          + positively (within business-hours)
          + negatively (outside leisure-time)
    7. [91]rewrite/redirect URLs based on any reasonable combination of
          + [92]string/regular expression editing  la sed with
          + silent squid redirecting rewrite (s@from@to@[i])
          + visible client redirecting rewrite (s@from@to@[i]r) ***)
          + [93]URL replacement with
          + silent squid redirect to a common URL (redirect "new_url")
          + visible client redirect to a common URL
            (redirect "302:new_url") ***)
       activated by
          + [94]1-1 URL redirection
          + [95]destination group match
          + [96]a fallback/default for blocked URLs
          + [97]a fallback/default for blocked/unknown clients
       and optionally with
          + [98]runtime string substitution  la strftime or printf
    8. [99]define access control lists (acl) based on any reasonable
       combination of the definitions above by
          + giving each source (user/client) group
          + [100]a pass list with any reasonable combination of
          + acceptable destination groups (good-dests ...)
          + unacceptable destination groups (!bad-dests ...)
          + [101]block IP address URLs (enforce the use of domain names)
            (!in-addr)
          + [102]wildcards/nothing (any|all|none)
    9. optionally [103]a common rewrite rule set for the source group
   10. optionally [104]a default replacement URL for blocked destinations
       for the source group
       
        and optionally:
                
   11. link the acl to a given time space
          + positively (within business-hours)
          + negatively (outside leisure-time)
   12. [105]defining a fallback/default ruleset
   13. have selective logging by optional log statements in the: ****)
          + [106]source/client group declarations to log all translations
            for the group (log "file")
          + [107]destination group declarations. Typically used to log
            blacklist matches. (log "file")
          + [108]rewrite rule group declarations to log all translations
            for the rule set (log "file")
       and optionally anonymized to protect the individuals
       (log anonymous "file")
       
   *) Client access control based on domain name requires enabling
   reverse lookups (log_fqdn on) in squid.conf.
   **) Client access control based on user id requires enabling
   RFC931/ident in squid.conf. Note: The RFC931/ident configuration is
   changed in squid-2.2 and the RFC931/ident support is broken in
   squid-2.2 at least up to STABLE2. We currently recommend using
   [109]squid-2.1.PATCH2 in production if RFC931 is used.
   ***) Note: Visible redirects (302:new-url) are not supported by some
   interim versions of Squid (presumably 1.2-2.0).
   ****) Note: squidGuard is smart enough to open only one filedescriptor
   per logfile (i.e. not necessarily one per log statement); per spawned
   process of course. Though logging to too many different files may
   exeed your system's concurrent filedescriptor limit. 
   
Portability

   squidGuard should compile right out of the box on any modern brand of
   UNIX with a [110]development environment and a recent version (2.X) of
   the [111]Berkeley DB library. squidGuard is developed on [112]Sun
   [113]Solaris-2.6 with [114]gcc-2.7.2.3, [115]bison-1.25,
   [116]flex-2.5.4. We also test regularly on [117]Linux/RedHat-5.2 with
   gcc-2.8.1 and [118]Digital UNIX/OSF1-4.0 with gcc-2.7.2.3. We always
   use [119]our most recent copy of the [120]Berkeley DB.
   
   Users have reported success on at least, but not limited to:
     * AIX: 4.1.3, 4.3.2.0/egcs-2.91.66
     * Dec-Unix: OSF1-4.0/gcc-2.7.2.3, 3.2C/gcc-2.7.2.3
     * Linux: RedHat-5.2/gcc-2.8.1
     * Solaris: 2.6/gcc-2.7.2.3
       
   Please [121]report missing list entries.
   
[122]Installation guide

   The [123]installation guide is in a [124]separate document.
   
[125]Configuration

   The [126]Configuration is in a [127]separate document.
   
A glimpse behind the curtain

  How squidGuard comunicates with Squid
  
   squidGuard uses Squid's [128]standard redirector interface. When Squid
   is used with squidGuard:
     * Squid spawns a configurable number of squidGuard subprocesses at
       startup.
     * For each request Squid receives, it sends a line of the format
       
        URL ip-address/fqdn ident method\n
                
       through a pipe to a squidGuard subprocesses on its stdin. ("\n" is
       the newline character.)
       Note: This is after a possible insertion of the value for
       "append_domain" by Squid (See squid.conf).
     * squidGuard checks the received info with the configured access
       control lists and decides whether the URL should pass unchanged or
       not.
     * squidGuard then sends a line through its stdout via a pipe back to
       Squid. The format is
       
        \n
                
       or
       
        new_URL ip-address/fqdn ident method\n
                
       for passed URLs and modified/blocked URLs respectively. By default
       the redirect is done by Squid silently and invisible for the
       user/browser. The new URL can be prepended with "302:" to make the
       redirect visible for the user by asking the browser to request the
       new URL.
       Note: A Squid redirector cannot really block an URL; it must
       redirect it to something (preferably an empty image, a stopsign
       image, a dummy access denied page or a more or less intelligent
       and informative page (CGI)).
     * On a HUP signal Squid terminates all its redirector subprocesses
       (squidGuard) and starts new fresh ones.
     * On exit (a TERM signal) Squid terminates all its redirector
       subprocesses (i.e. squidGuard) too.
     * A redirector subprocesses (i.e. squidGuard) must never exit while
       Squid is running. Though Squid will recover from crashed
       redirector subprocess problems with a HUP signal. Anyway
       squidGuard has proven rock solid so far.
       
  How squidGuard decides what to do
  
   For each request squidGuard will:
     * try to find a matching client group based on the client IP-address
       and optional domainname and user ID information. Note: The client
       groups are matched in the order they are defined. Thus a client
       group that is a subset of a more general group must come first of
       the two to take effect. If the client does not match a group then
       the default acl will be used.
       Note: The client information must match at least one of each
       defined type within the actual group to qualify (i.e. ip AND
       domain AND user).
     * select the corresponding active acl. If no corresponding acl is
       active or defined the default acl is selected.
     * try to match the URL to each destination group in the listed order
       in the pass rule in the actual acl and for each destination group
       in the priority order domainlist, urllist and expressionlist.
       Note: It is sufficient that the URL matches one of the defined
       types within the actual group to qualify (i.e. domainlist OR
       urllist OR expressionlist).
     * if a negative group ("!group") is matched, return the redirect URL
       for that destination group if defined or alternatively the
       redirect URL in the actual acl if defined or else the redirect URL
       in the default acl as the last resort.
     * when a positive group ("group") is matched the stop searching.
     * apply the rewrite rules for the matched destination group if any
       and then apply rewrite rules for the acl if any or else the
       rewrite rules for the default acl if any.
     * if the URL was changed by a rewrite rule return the new URL and
       the suplied information.
     * Otherwise return an empty line indicating no change to Squid.
       
  What makes squidGuard so fast and robust
  
   The main design goals for squidGuard were, and still are:
     * robust and modular code already from the start
     * good coding standard
     * efficient code and dessign
     * use of existing robust libraries, OS native or free, where
       appropriate
       
   The efficiency is achieved by:
     * storing all lists in B-trees.
     * compiling/optimizing all regular expressions at startup.
     * source code in C.
     * using custom-made string comparators where regular expression
       match would be an overkill.
     * using a cursor to check the previous key in B-trees to speed up
       substring matching.
     * chosing the more efficient system libraries/calls where there are
       alternatives.
     * breaking out from the rule checking loops as son as a decision can
       be made.
     * avoiding constant evaluation of the rule's time space validity by
       using valid/disabled flags. At startup the initial state of the
       time dependent rules are evaluated and an alarm is set for the
       first moment of change. When the alarm goes off squidGuard
       reevaluates all its time dependent rules and sets a new alarm,
       etc. etc.
       
   The robustness is achieved by:
     * actively trying to do things the right way already from the start.
     * focusing on and implementing one module at the time.
     * using the well proven Berkeley DB library to achieve much with
       simple code.
     * using lex and yacc to make a simple and flexible configuration
       file parser that is easy to modify and extend.
     * using gcc -Wall -W... to avoid common errors.
     * publicly reviewable open source code.
       
  Special notes, features and oddities
  
   Please note:
     * If something is terribly wrong (like syntax error in
       squidGuard.conf) squidGuard will fallback to a pass all for all
       mode. This is an intensional feature not a bug! squidGuard can't
       resume normal operation from this mode without being restarted by
       a HUP signal to Squid (not squidGuard).
     * The client groups are matched in the order they are defined. Thus
       a client group that is a subset of a more general group must come
       first of the two to take effect.
     * The URL and domain matching is case insensitive. Thus
       
        http://www.what.ever.com/where/ever
                
       and
       
        http://wWw.wHat.evER.com/Where/Ever
                
       doesn't matter.
     * The protocol (proto://) prefixes are ignored by squidGuard in both
       domain and URL matching, but not in the regex matching.
     * Domain matching includes subdomains. Thus if you have a domainlist
       containing bad.com all these URLs will match that destination
       group since they are equal to or subdomains of bad.com:
       
        http://bad.com
                http://bad.com/whatever
                ftp://bad.com
                wais://bad.com
                http://www2.bad.com
                http://whatever.bad.com
                http://www56.whatever.bad.com
                
       but not:
       
        http://www.verybad.com
                
       unless www.verybad.com or verybad.com is in that list too.
     * The domain prefixes www[0-9]? and web[0-9]? are ignored by
       squidGuard in URL matching. Thus if you have an urllist containing
       "bar.com/~baduser" then all these URLs will match that destination
       group:
       
        http://bar.com/~baduser
                http://www.bar.com/~baduser/whatever
                http://www2.bar.com/~baduser/whatever/bar.html
                
       but not:
       
        http://foo.bar.com/~baduser
                
       unless foo.bar.com/~baduser is in that list too.
     * squidGuard will match subpaths for URLs. Thus if you have an
       urllist containing "foo.bar.com/~baduser" then all these URLs will
       match that destination group:
       
        http://foo.bar.com/~baduser
                http://foo.bar.com/~baduser/
                http://foo.bar.com/~baduser/index.html
                http://foo.bar.com/~baduser/whatever/foo.html
                http://www.foo.bar.com/~baduser/whatever
                http://www2.foo.bar.com/~baduser/whatever/bar.html
                
       but not:
       
        http://foo.bar.com/~baduserhome
                
       nor
       
        http://foo.bar.com/~gooduser
                http://foo.bar.com/~gooduser/foo.html
                http://foo.bar.com/~gooduser/whatever/bar.html
                
       unless foo.bar.com/~baduserhome and/or foo.bar.com/~gooduser is in
       that list too.
     * Currently a squidGuard process will reincarnate on a HUP signal
       directly to the squidGuard process -- if at all possible (i.e.
       execvp() and replace itself with a fresh squidGuard process with
       the same command line arguments). Thus if you suspect a squidGuard
       process has gone mad, you don't necessarily need to reconfigure
       Squid; a "kill -HUP that_squidGuard_pid" will probably do.
       
  News and changes
  
   Major news and changes in
          1.1.1:
          
          + Lots of bug fixed.
            
          1.1.0:
          
          + Brought the doc up to date.
            
          1.1.0.beta1:
          
          + Added support for prebuilt database files. squidGuard will
            now fire instantly even with a million entry blacklist, use
            less RAM and perform only marginally slower than with the
            same databases in-memory-only. This is done transparently in
            such a way that if you have the config:
            
              dest foo {
                      
                    domainlist foo/domains
                            
                      }
                      
            and "dbhome/foo/domains.db" exists then
            "dbhome/foo/domains.db" will be used regardless if
            "dbhome/foo/domains" exists or not.
            
              "squidGuard -C file" (re)builds file.db from list file and
                      exits. Note file is relative to dbhome unless
                      absolute. Also note "squidGuard -C all" (re)builds
                      databases for all defined lists.
                      
            Note: Prebuilt database are currently only supported for
            domainlists and urllists in the destination groups. We plan
            to add support for this to the userlist and iplist in the
            source groups soon.
          + Added support for runtime updates in prebuilt database files
            without signal or restart.
            
              "squidGuard -u" updates all defined databases (file.db)
                      from ditto file.diff where found and exits. Note
                      file.diff has the simple format:
                      
                    +entry_to_be_added
                            -entry_to_be_removed
                            ...
                            
                      (i.e. not the common patch format)
                      
          + Added %p for the path part (without the leading "/") in the
            runtime substitution. Thus you may find this urllist syntax
            useful for hostredirection:
            
              foo.bar http:hotell.server/foo.bar/%p
                      
          + Added support for old K&R compilers through CPP magic
            inspired by the original MIT X11 coding standard. So an
            ANSI-C compiler is no longer requiered, though gcc is still
            recommended.
          + Added an up to date 25k entries blacklist; now regularly
            updated and published separately in the distribution
            directory.
          + Contributed the squidGuardRobot. Currently completely
            undocumented and not recommended for the average site.
          + Fixes: All known bugs were fixed, including:
               o building with the DB library installed in odd places.
               o building with native lex.
               o userlist exact match bug.
               o should match with the full hostname against domainlist
                 (i.e. not strip www-prefix etc. here). Thus a domainlist
                 may now contain a hostname like www.foo.bar if you only
                 want match with that host and not www2.foo.bar or
                 whatever.
               o some potential buffer overflows.
            
          1.0.0:
          
          + userlist: Now accepts a file like /etc/passwd, .htpasswd etc.
            
          1.0.0.beta3:
          
          + Debuging/testing: Added -t option to simplify
            [129]simulation/testing of time constraints
            (squidGuard -t yyyy-mm-ddTHH:MM:SS)
            
          1.0.0.beta2:
          
          + All objects and default ACL: Optional logging of altered
            requests (log file)
          + Source objects: User lists in files (userlist file)
          + Source objects: IP lists in files (iplist file)
          + CGI: Added a brand new squidGuard.cgi in samples/ with
            configurable strings, optional reverse lookup with
            autoredirect for in-addr and more.
          + Fixes: All known bugs were fixed.
          + General: Rewritten common logging functions.
          + General: Completed the new comprehensive online documentation
            ([130]http://info.ost.eltele.no/freeware/squidGuard/)
            
          1.0.0.beta1:
          
          + New object: time (time name {...})
          + New built in: in-addr (pass ... !in-addr ...)
          + All objects and ACLs: Optional time constraints
            (... within|outsidename {...} [else {...}])
          + Optimization: Major code review. Now faster than ever in
            spite of more functionality.
          + Build: Adapted GNU autoconfigure.
          + Fixes: All known bugs were fixed.
          + General: Established an official home page with new
            comprehensive documentation
            ([131]http://info.ost.eltele.no/freeware/squidGuard/)
            
   Se the [132]change log for the details and minor changes
   
  Known bugs and misfeatures
  
   We have had squidGuard runing on our Squid proxy for more than a year
   now with about 5-11000 listed domains, 6-14000 listed URLs, 3 complex
   regular expressions and 20-25 acls whereof some with timeconstrains.
   So far we haven't seen a single crash, coredump or hang caused by
   squidGuard in production. Although squidGuard has proven rock solid
   there still are some known minor problems:
     * Not anymore; All known problems have been fixed in
       squidGuard-1.1.0.beta1. Though it includes some new functionality
       that may have introduced new bugs we haven't discovered yet.
       
  To do or not to do
  
   That is the question.. Here are some possible development issues we
   have discussed:
   
   Put host addresses in IP lists into B-tree
          This should dramaticly reduce the performance penalty of long
          lists of random client addresses. We should still keep IP
          ranges in sequentially linked lists since ranges of random
          width are hard to index efficiently.
          
   Add syslog support
          Maybe we should add syslog support as an alternative for the
          squidGuard.log.
          
   Include support for classless IP ranges in the domainlists
          We have to find a good storage method and modify the domain
          comparator slightly to select IP range mode if the URL host is
          an IP address. IP range comparision is allready in use in the
          client group match so it shouldn't be to hard.
          
   Benchmarking alternative regexp libraries
          Configure should automaticly select the best regexp library;
          native or GNU/FSF.
          
   Reconfigure on a HUP signal directly to squidGuard
          In the beginning where we used only one redirector process,
          this seemed like a good idea. I really don't know why one
          should use more squidGuard redirectors than CPUs on the system
          but that seems to be recommended. So therefor we have got
          second thoughts about this since it raises a real challenge to
          find a way to reconfigure all the redirectors with one signal.
          Either this should be done by having the good Squid guys
          implement a signal handler for a dedicated signal that is
          passed to the redirector processes or that makes Squid send a
          HUP signal to its redirectors. Alternatively this has to be
          done by some kind of IPC. Maybe SysV IPC semaphores is an
          option here, but this is likely to reduce the portability and
          increase the complexity of squidGuard.
          
   Preventing users from accessing blocked sites by using their IP
          address after a manual nslookup
          This is partially done by the new optional !in-addr flag. An
          alternative path with non blocking reverse lookups before group
          matching have been left since it complicates things too much at
          the present. An alternative is to use a simple Perl script to
          include both the domainname and the IP addresses in the lists
          
   A shared database engine
          When running multiple squidGuard processes it is of course a
          waist of RAM to have each processes hold a complete private
          copy of the destination databases in memory. This is now solved
          with the new support for prebuilt on-disk databases. Though
          there are other possible solutions to avoid this too:
          
          + Spawn only one squidGuard process. This may be the best
            solution on a single CPU system anyway.. And maybe increase
            squidGuard's priority (renice(1)) manually if Squid warns
            about growing redirector queue.
          + Have a common database engine process with concurrent access
            by the squidGuard processes through IPC. This raises a real
            challenge to handle problems like:
               o Who should spawn the database engine process and how
                 should it be done to avoid race conditions?
               o How should the processes comunicate -- through pipes or
                 SysV IPC?
               o How to implement robustness in case one process in the
                 "cluster" crashes?
               o What about portability between BSD and SysV systems?
            
   -- Comments and contributions are [133]welcome.
   
FAQ - Frequently Asked/Answered Questions

   The [134]FAQ is in a [135]separate document.
   
Links to related documentation

   Here is a guide to related documentation
   
   [136]A happy user's squidGuard page :-)
          [137]Fabrice Prigent, Network Administrator at the
          [138]University of Toulouse, France, has written an excellent
          page about squidGuard in both [139]French and [140]English. He
          has done a [141]neutral comparison of known free redirectors
          for Squid. He also has links to some [142]URL/domain
          lists/patterns you may find useful in conjunction with Squid
          and squidGuard.
          
   [143]The official Squid 1.1 Release Notes:
          The Squid programmers/authors original documentation on Squid's
          redirector interface.
          
   [144]The official Squid redirector FAQ:
          Frequently Answered Questions about Squid redirectors.
          
   [145]The official Squid ralated software FAQ:
          Pointers to Squid redirector packages and more.
          
   [146]The official Squid FAQ:
          Answers to almost all your questions about Squid.
          
   [147]Squid related documentation:
          Pointers to even more Squid related documentation.
          
Useful software links

   Here is a guide to more or less free software tools you may or may not
   need.
   
   [148]squidGuard:
          Well, that is what this is all about :-)
          
   [149]Squid:
          If you don't have Squid you don't need squidGuard either. You
          may prefer to download [150]our copy if you are in Europe or
          have trouble reaching [151]the Squid home page.
          
   [152]libdb.a - Berkeley DB - The Berkeley Database library version
          2.X:
          squidGuard requires this library. You must install a version
          2.X of DB if your system does not already have it or it has a
          version 1.X installed (Version 1.X and 2.X may coexist on a
          system). The Berkeley Database library can be used [153]free of
          charge with squidGuard since squidGuard is [154]GPL. You may
          prefer to download [155]our copy if you are in Europe or have
          trouble reaching [156]Sleepycat.
          Note: All versions of the Berkeley Database library are called
          betas. In contrast to the normal use of the notion beta this
          does not mean that the Berkeley Database library is in unstable
          prerelease state. Quite contrary, it has proven to be very
          stable and can safely be used in production quality software.
          
   [157]Gzip - GNU's replacement for compress:
          You need [158]gzip/gunzip/zcat to unzip the squidGuard
          distribution. If you ever plan to work with freeware for
          UNIX-like environments then [159]gzip/gunzip/zcat is a must.
          You may prefer to download [160]our copy if you are in Europe
          or have trouble reaching [161]The Free Software Foundation or
          finding a good [162]mirror.
          
   [163]Gmake - GNU make:
          If you don't have a development environment with a "make"
          compatible build tool and stuff listed below, then the
          [164]Free Software Foundation is your best friend. The Free
          Software Foundation makes free versions of everything you need
          to set up a development environment for UNIX-like systems.
          Besides the University of California, Berkeley/[165]Berkeley
          Software Design, the free software from the [166]Free Software
          Foundation is the main reason there are things called 386bsd,
          NetBSD, FreeBSD, Linux, etc. etc. Thanks to the constant open
          source revision and refinement via the Internet over the years
          since 1983, the Free Software Foundation in most cases makes
          faster, better and less buggy reincarnations of most UNIX-like
          tools an libraries than the commercial vendors do and the code
          runs on almost any UNIX-like platform you can think of so you
          can set up a more uniform environment on a multivendor fleet.
          Therefor we recommend using [167]GNU tools wherever you can!
          You may prefer to download [168]our copy if you are in Europe
          or have trouble reaching [169]The Free Software Foundation or
          finding a good [170]mirror.
          
   [171]Gcc - The GNU C Compiler:
          If you don't have an ANSI C compiler then the [172]Free
          Software Foundation is your best friend. Gcc makes faster and
          less buggy code than many commercial compilers and runs on
          almost any UNIX-like platforms you can think of, so we
          recommend using it anyway unless your commercial compiler is
          really clever. squidGuard is developed mainly with gcc-2.7.2.3.
          (The new gcc-2.8.x may be fine too.) You may prefer to download
          [173]our copy if you are in Europe or have trouble reaching
          [174]The Free Software Foundation or finding a good
          [175]mirror.
          
   [176]Bison - The GNU/FSF parser generator, Bison:
          
   [177]Byacc - The Berkeley Yacc parser generator:
          If you for some strange reason don't have a "yacc" (Yet Another
          Compiler Compiler) compatible parser generator then [178]The
          GNU/FSF parser generator, (bison) and [179]The Berkeley Yacc
          parser generator (byacc) are your friends. You need yacc, byacc
          or bison to compile src/sg.y into src/y.tab.c and src/y.tab.h.
          Bison makes faster parsers than most commercial versions of
          yacc, so we recommend using it anyway as long as its copyright
          isn't a problem for you (You may not use Bison to build
          commercial software). If you can't use Bison and lack yacc, use
          byacc which has a more liberal copyright. (Though the parser
          speed doesn't matter much for squidGuard since it is used for
          parsing the config file only). You may prefer to download our
          copies of [180]bison and/or [181]byacc if you are in Europe or
          have trouble downloading from the sources.
          
   [182]Flex - The Fast Lexical Analyzer Generator:
          If you for some strange reason don't have a "lex" compatible
          lexical analyzer generator then the [183]Fast Lexical Analyzer
          Generator (flex) is your friend. You need lex/flex to compile
          src/sg.l into src/lex.yy.c. Flex makes faster scanners than
          many (most/all?) commercial versions of lex, so we recommend
          using it anyway. (Though the lexer speed doesn't matter much
          for squidGuard since it is used for parsing the config file
          only). squidGuard is developed mainly with flex-2.5.4a. You may
          prefer to download [184]our copy if you are in Europe or have
          trouble reaching [185]The Free Software Foundation or finding a
          good [186]mirror.
          
   [187]Regex - the GNU regex library:
          
   [188]Rx - A fast replacement for the GNU regex library:
          squidGuard must be linked with a regular expression library
          that supports regcomp() and regexec(). If your system for some
          strange reason don't have this the GNU [189]regex or [190]rx
          libraries may be good alternatives. We haven't done any
          comparison of these libraries yet, but have successfully linked
          squidGuard with both. These may be faster than many commercial
          variants anyway, so you may consider using one of them even if
          your system have a compatible library. Finding a fast regular
          expression executer, regexec(), may be critical for good
          performance if you run squidGuard with many and/or complex
          regular expressions. The performance of the regular expression
          compiler regcomp() is less critical since all expression
          compilation is done at load time, not when handling requests.
          You may prefer to download [191]our copies if you are in Europe
          or have trouble reaching [192]The Free Software Foundation or
          finding a good [193]mirror.
          
   [194]Apache - The [195]most popular web server on the Internet:
          Although your redirectors could point to nonexisting URLs, it
          would be a better idea in most configurations to redirect to
          existing URLs. So you probably need a web server. If you don't
          have a web server we strongly recommend [196]Apache. You can
          install it on the proxy server or a nearby server. You may
          prefer to download [197]our copy if you are in Europe or have
          trouble reaching the [198]apache.org or finding a good
          [199]mirror.
          
   [200]Perl - The popular all in one language:
          You don't really need Perl to run squidGuard, but it comes very
          handy when making CGI scripts, HTML parsers, URL collectors,
          database compactors etc. etc. You may prefer to download
          [201]our copy if you are in Europe or have trouble reaching the
          [202]perl.com or finding a good [203]mirror.
          
   [204]Identd - [205]our free ident daemon for M$ Windoze:
          
   [206]Pidentd - a free Portable Ident Daemon for Unix:
          To be able to use [207]user IDs in the [208]client rules
          definitions the actual clients must support
          [209]RFC931/[210]RFC1413. [211]Pidentd is for Unix and
          [212]Identd for M$ Windoze. Feel free to download our copy of
          [213]pidentd or our official distribution of [214]identd.
          
   [215]squidlog2combined:
          squidlog2combined is a free tool that lets you convert native
          Squid accesslogs to the Apache combined log format, suitable
          for log analyzers like [216]Webalizer and others. It has some
          [217]really nice options.
          
   [218]Webalizer -a free web server log file analyzer:
          [219]Webalizer is a fast, free web server log file analysis
          program. It produces highly detailed, easily configurable usage
          reports in HTML format, for viewing with a standard web
          browser. With Squid you may find it usefull in combination with
          [220]squidlog2combined and [221]Apache's logresolve. Feel free
          to download [222]our copy.
          
   Note: [223]ftp.ost.eltele.no is not mirroring other sites. We just put
   a copy there, to have it handy, of what we manually download and find
   useful. The copies are unchanged from the original but may have been
   compressed with [224]gzip (.gz) if the original was compressed with
   the old compress (.Z). 
   
Copyright

   squidGuard is covered by the [225]GNU General Public Licence (GPL).
   The copyright boils down to:
     * You may use squidGuard in both free and commercial services
       without fee or registration to [226]ElTele st AS.
     * You may freely redistribute unchanged free copies of squidGuard;
       precompiled or in source form.
     * There is no warranty for squidGuard.
     * You may not change the copyright.
     * You may not sell or use squidGuard in a commercial software
       package without a written agreement with [227]ElTele st AS; and
       most likely with [228]Sleepycat too for the DB part.
       
   For more copyright details you have to read the [229]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
   [230]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 [231]very welcome too.. They makes [232]us even
   more enthusiastic!
   
Authors

   squidGuard was designed by [233]Pl Baltzersen and implemented by
   [234]Lars Erik Hland
   at [235]ElTele st AS and made freely available by permission of
   [236]ElTele st AS.
   
   This page is written and maintained by [237]Pl Baltzersen.
   Please [238]report any errors, broken links, missing stuff, typos,
   misspellings, wrong grammar, norwenglish phrases etc. you discover.
   
Contributors

   Thanks to:
          [239]Gary Lindstrom, [240]Fabrice Prigent. [241]Jiri A. Randus.
          [242]Joseph Lesko.
          
      [243][gnu-logo.gif] [244][perl-logo.gif] [245][solaris-logo.gif]
                [246][sun-logo.gif] [247][eltele-logo.gif] 
                                      
    [248][apache-logo.gif] [249][squid-logo.gif] [250][squidGuard.gif] 
                                      
                             [251][identd.gif] 

References

   1. http://www.ost.eltele.no/
   2. http://info.ost.eltele.no/freeware/squidGuard/
   3. http://ftp.ost.eltele.no/pub/www/proxy/squidGuard/
   4. http://info.ost.eltele.no/freeware/squidGuard/print.shtml
   5. http://info.ost.eltele.no/freeware/squidGuard/print.shtml
   6. http://info.ost.eltele.no/freeware/squidGuard/faq.shtml
   7. http://info.ost.eltele.no/freeware/squidGuard/faq.shtml
   8. http://ftp.ost.eltele.no/pub/www/proxy/squidGuard/ANNOUNCE
   9. http://ftp.ost.eltele.no/pub/www/proxy/squidGuard/ANNOUNCE
  10. http://info.ost.eltele.no/freeware/squidGuard/#Contents
  11. http://info.ost.eltele.no/freeware/squidGuard/#Downloading
  12. http://info.ost.eltele.no/freeware/squidGuard/#Introduction
  13. http://info.ost.eltele.no/freeware/squidGuard/#Capabilities
  14. http://info.ost.eltele.no/freeware/squidGuard/#Portability
  15. http://info.ost.eltele.no/freeware/squidGuard/installation.shtml
  16. http://info.ost.eltele.no/freeware/squidGuard/installation.shtml#Quick_install
  17. http://info.ost.eltele.no/freeware/squidGuard/installation.shtml#Detailed_install
  18. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml
  19. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Configuration_file
  20. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#General
  21. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Structure
  22. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Reserved
  23. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Lables
  24. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Breaking
  25. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Directories
  26. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Timespace
  27. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Sourcegroups
  28. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Destinationgroups
  29. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Rewritegroups
  30. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Acls
  31. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Lists
  32. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Domainlists
  33. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#URLlists
  34. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Expressionlists
  35. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Tuning
  36. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Examples
  37. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Minimal
  38. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#example01
  39. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#example02
  40. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#example03
  41. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#example04
  42. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#example05
  43. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#example06
  44. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#example07
  45. http://info.ost.eltele.no/freeware/squidGuard/#Internals
  46. http://info.ost.eltele.no/freeware/squidGuard/#API
  47. http://info.ost.eltele.no/freeware/squidGuard/#ACL evaluation
  48. http://info.ost.eltele.no/freeware/squidGuard/#Efficiency
  49. http://info.ost.eltele.no/freeware/squidGuard/#Notes
  50. http://info.ost.eltele.no/freeware/squidGuard/#Changes
  51. http://info.ost.eltele.no/freeware/squidGuard/#Bugs
  52. http://info.ost.eltele.no/freeware/squidGuard/#Todo
  53. http://info.ost.eltele.no/freeware/squidGuard/faq.shtml
  54. http://info.ost.eltele.no/freeware/squidGuard/#Doc Links
  55. http://info.ost.eltele.no/freeware/squidGuard/#Software links
  56. http://info.ost.eltele.no/freeware/squidGuard/#Copyright
  57. http://info.ost.eltele.no/freeware/squidGuard/#Feedback
  58. http://info.ost.eltele.no/freeware/squidGuard/#Authors
  59. http://info.ost.eltele.no/freeware/squidGuard/#Contributors
  60. http://ftp.ost.eltele.no/pub/www/proxy/squidGuard/
  61. ftp://ftp.ost.eltele.no/pub/www/proxy/squidGuard/
  62. http://ftp.ost.eltele.no/pub/www/proxy/squidGuard/squidGuard-1.1.1.tar.gz
  63. http://ftp.ost.eltele.no/pub/www/proxy/squidGuard/sample-blacklist.tar.gz
  64. http://info.ost.eltele.no/freeware/squidGuard/#Changes
  65. http://info.ost.eltele.no/freeware/squidGuard/#Bugs
  66. http://squid.nlanr.net/
  67. http://info.ost.eltele.no/freeware/squidGuard/#Copyright
  68. http://info.ost.eltele.no/freeware/squidGuard/#Capabilities
  69. http://cache.univ-tlse1.fr/documentations/cache/squidguard_en.html#Comparison
  70. http://info.ost.eltele.no/freeware/squidGuard/#Installation
  71. http://info.ost.eltele.no/freeware/squidGuard/#Portability
  72. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Sample adultdb
  73. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml
  74. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Timespace
  75. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Daily
  76. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Weekly
  77. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Date
  78. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Daterange
  79. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Datewildcard
  80. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Sourcegroups
  81. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#IP
  82. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#IPlist
  83. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Domain
  84. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#User
  85. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Destinationgroups
  86. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Domainlist
  87. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Domainlist
  88. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#URLlist
  89. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#URLlist
  90. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Expressionlist
  91. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Rewritegroups
  92. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Rewritegroups
  93. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Redirect
  94. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#URL redirect
  95. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Destinationgroup redirect
  96. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Redirect
  97. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Default
  98. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Redirect
  99. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Acls
 100. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Pass
 101. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Builtin
 102. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Builtin
 103. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Rewrite
 104. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Redirect
 105. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Default
 106. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Clientgroup log
 107. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Destinationgroup log
 108. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#Rewrite log
 109. http://squid.nlanr.net/Squid/v2/2.1/squid-2.1.PATCH2-src.tar.gz
 110. http://info.ost.eltele.no/freeware/squidGuard/installation.shtml#Detailed_install_1
 111. http://info.ost.eltele.no/freeware/squidGuard/installation.shtml#Detailed_install_2
 112. http://www.sun.com/servers/
 113. http://www.sun.com/solaris/
 114. http://info.ost.eltele.no/freeware/squidGuard/#Gcc
 115. http://info.ost.eltele.no/freeware/squidGuard/#Bison
 116. http://info.ost.eltele.no/freeware/squidGuard/#Flex
 117. http://www.redhat.com/
 118. http://www.unix.digital.com/
 119. http://ftp.ost.eltele.no/pub/db/
 120. http://www.sleepycat.com/db/
 121. mailto:squidguard@ost.eltele.no?subject=SquidGuard%20success%20report
 122. http://info.ost.eltele.no/freeware/squidGuard/installation.shtml
 123. http://info.ost.eltele.no/freeware/squidGuard/installation.shtml
 124. http://info.ost.eltele.no/freeware/squidGuard/installation.shtml
 125. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml
 126. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml
 127. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml
 128. http://squid.nlanr.net/Squid/1.1/Release-Notes-1.1.txt
 129. http://info.ost.eltele.no/freeware/squidGuard/faq.shtml#testing_timeconstraints
 130. http://info.ost.eltele.no/freeware/squidGuard/
 131. http://info.ost.eltele.no/freeware/squidGuard/
 132. http://ftp.ost.eltele.no/pub/www/proxy/squidGuard/CHANGELOG
 133. mailto:squidguard@ost.eltele.no
 134. http://info.ost.eltele.no/freeware/squidGuard/faq.shtml
 135. http://info.ost.eltele.no/freeware/squidGuard/faq.shtml
 136. http://cache.univ-tlse1.fr/documentations/cache/squidguard_en.html
 137. http://cache.univ-tlse1.fr/les.personnes/fabrice.prigent
 138. http://www.univ-tlse1.fr/
 139. http://cache.univ-tlse1.fr/documentations/cache/squidguard.html
 140. http://cache.univ-tlse1.fr/documentations/cache/squidguard_en.html
 141. http://cache.univ-tlse1.fr/documentations/cache/squidguard_en.html#Comparison
 142. http://cache.univ-tlse1.fr/documentations/cache/squidguard_en.html#contrib
 143. http://squid.nlanr.net/Squid/1.1/Release-Notes-1.1.txt
 144. http://squid.nlanr.net/Squid/FAQ/FAQ-15.html
 145. http://squid.nlanr.net/Squid/FAQ/FAQ-21.html#ss21.4
 146. http://squid.nlanr.net/Squid/FAQ/FAQ.html
 147. http://squid.nlanr.net/Squid/documentation.html
 148. http://ftp.ost.eltele.no/pub/www/proxy/squidGuard/
 149. http://squid.nlanr.net/
 150. http://ftp.ost.eltele.no/pub/www/proxy/squid/
 151. http://squid.nlanr.net/
 152. http://www.sleepycat.com/db/
 153. http://www.sleepycat.com/db/licensing.html
 154. http://www.gnu.org/copyleft/gpl.html
 155. http://ftp.ost.eltele.no/pub/db/
 156. http://www.sleepycat.com/
 157. ftp://ftp.gnu.org/gnu/gzip/
 158. http://www.gnu.org/software/gzip/
 159. http://www.gnu.org/software/gzip/
 160. http://ftp.ost.eltele.no/pub/gnu/
 161. http://www.gnu.org/
 162. http://www.gnu.org/server/list-mirrors.html
 163. http://www.gnu.org/software/make/
 164. http://www.gnu.org/
 165. http://www.bsd.com/
 166. http://www.gnu.org/
 167. http://www.gnu.org/
 168. http://ftp.ost.eltele.no/pub/gnu/
 169. http://www.gnu.org/
 170. http://www.gnu.org/server/list-mirrors.html
 171. http://www.gnu.org/software/gcc/
 172. http://www.gnu.org/
 173. http://ftp.ost.eltele.no/pub/gnu/
 174. http://www.gnu.org/
 175. http://www.gnu.org/server/list-mirrors.html
 176. ftp://ftp.gnu.org/gnu/bison/
 177. ftp://ftp.cs.berkeley.edu/ucb/4bsd/
 178. http://www.gnu.org/software/bison/
 179. ftp://ftp.cs.berkeley.edu/ucb/4bsd/
 180. http://ftp.ost.eltele.no/pub/gnu/
 181. http://ftp.ost.eltele.no/pub/unix/system/
 182. ftp://ftp.gnu.org/gnu/flex/
 183. ftp://ftp.gnu.org/gnu/flex/
 184. http://ftp.ost.eltele.no/pub/gnu/
 185. http://www.gnu.org/
 186. http://www.gnu.org/server/list-mirrors.html
 187. ftp://ftp.gnu.org/gnu/regex/
 188. ftp://ftp.gnu.org/gnu/rx/
 189. ftp://ftp.gnu.org/gnu/regex/
 190. ftp://ftp.gnu.org/gnu/regex/
 191. http://ftp.ost.eltele.no/pub/gnu/
 192. http://www.gnu.org/
 193. http://www.gnu.org/server/list-mirrors.html
 194. http://www.apache.org/httpd.html
 195. http://www.netcraft.com/survey/
 196. http://www.apache.org/httpd.html
 197. http://ftp.ost.eltele.no/pub/www/server/
 198. http://www.apache.org/
 199. http://www.apache.org/dyn/closer.cgi
 200. http://www.perl.com/
 201. http://ftp.ost.eltele.no/pub/perl/
 202. http://www.perl.com/
 203. http://www.perl.com/CPAN/SITES.html
 204. http://info.ost.eltele.no/freeware/identd/
 205. http://www.ost.eltele.no/
 206. http://www.lysator.liu.se/~pen/pidentd/
 207. http://info.ost.eltele.no/freeware/squidGuard/configuration.shtml#User
 208. http://info.ost.eltele.no/freeware/squidGuard/#Capabilities
 209. http://ftp.ost.eltele.no/pub/networking/ident/rfc931.txt
 210. http://ftp.ost.eltele.no/pub/networking/ident/rfc1413.txt
 211. ftp://ftp.lysator.liu.se/pub/ident/servers/
 212. http://info.ost.eltele.no/freeware/identd/
 213. http://ftp.ost.eltele.no/pub/networking/ident/unix/
 214. http://info.ost.eltele.no/freeware/identd/
 215. http://info.ost.eltele.no/freeware/misc/#squidlog2combined
 216. http://info.ost.eltele.no/freeware/squidGuard/#Webalizer
 217. http://info.ost.eltele.no/freeware/misc/#squidlog2combined
 218. http://www.mrunix.net/webalizer/
 219. http://www.mrunix.net/webalizer/
 220. http://info.ost.eltele.no/freeware/misc/#squidlog2combined
 221. http://www.apache.org/
 222. http://ftp.ost.eltele.no/pub/www/server/util/
 223. http://ftp.ost.eltele.no/pub/
 224. http://info.ost.eltele.no/freeware/squidGuard/#Gzip
 225. http://www.gnu.org/copyleft/gpl.html
 226. http://www.ost.eltele.no/
 227. mailto:squidguard@ost.eltele.no?subject=squidGuard%20licensing
 228. http://www.sleepycat.com/db/licensing.html
 229. http://www.gnu.org/copyleft/gpl.html
 230. mailto:squidguard@ost.eltele.no
 231. mailto:squidguard@ost.eltele.no?subject=SquidGuard%20success%20report
 232. mailto:squidguard@ost.eltele.no
 233. mailto:pal.baltzersen@ost.eltele.no
 234. mailto:leh@nimrod.no
 235. http://www.ost.eltele.no/
 236. mailto:info@ost.eltele.no
 237. mailto:pal.baltzersen@ost.eltele.no
 238. mailto:squidguard@ost.eltele.no
 239. mailto:gplindstrom@exodus.nnc.edu
 240. mailto:fabrice.prigent@univ-tlse1.fr
 241. mailto:jiri.randus@inway.cz
 242. mailto:joe@nationnet.com
 243. http://www.gnu.org/
 244. http://www.perl.com/
 245. http://www.sun.com/solaris/
 246. http://www.sun.com/servers/
 247. http://www.ost.eltele.no/
 248. http://www.apache.org/httpd.html
 249. http://squid.nlanr.net/
 250. http://info.ost.eltele.no/freeware/squidGuard/
 251. http://info.ost.eltele.no/freeware/identd/
