
                                 SquidGuard

   [1]HOME [2]Downloads [3]Documentation [4]Development [5]Blacklists
   [6]Contributions [7]Contact

  Basic Configuration of squidGuard

   Once SquidGuard is successfully installed, you want to configure the
   software according to your needs. A sample configuration has been installed
   in the default directory  /usr/local/squidGuard (or whatever directory you
   pointed your installation to).
   Below you find three examples for the basic configuration of SquidGuard.
    1. Most simple configuration

       Most simple config uration: one category, one rule for all
#
# CONFIG FILE FOR SQUIDGUARD
#

dbhome /usr/local/squidGuard/db
logdir /usr/local/squidGuard/logs

dest porn {
        domainlist porn/domains
        urllist porn/urls
        }

acl {
        default {
                pass !porn all
                redirect http://localhost/block.html
        }
 }

       Make always sure that the very first line of your squidGuard.conf is not
       empty!
       The entries have the following meaning:

   dbhome Location of the blacklists
   logdir Location of the logfiles
   dest Definition of a category to block. You can enter the domain and url
   file along with a regular expression list (talk about regular expressions
   later on).
   acl  The actual blocking defintion. In our example only the default is
   displayed. You can have more than one acl in place. The category porn you
   defined in dest is blocked by the expression !porn. You have to add the
   identifier all after the blocklist or your users will not be able to surf
   anyway.
   The redirect directive is madatory! You must tell SquidGuard which page to
   display instead of the blocked one.
       > Choosing more than one category to block
       First you define your categories. Just like you did above for porn. For
       example:

       Defining three categories for blocking
dest adv {
        domainlist      adv/domains
        urllist         adv/urls
}
dest porn {
        domainlist      porn/domains
        urllist         porn/urls
}
dest warez {
        domainlist      warez/domains
        urllist         warez/urls
}

       Now your acl looks like that:

acl {
        default {
                pass    !adv !porn !warez all
                redirect http://localhost/block.html
                }
}

    2. Whitelisting
       Sometimes there is a demand to allow specific URLs and domains although
       they are part of the blocklists for a good reason. In this case you want
       to whitelist these domains and URLs.

       Defining a whitelist
dest white {
        domainlist      white/domains
        urllist         white/urls
}

acl {
        default {
                pass    white !adv !porn !warez all
                redirect http://localhost/block.html
                }
}

       In  this  example we assumed that your whitelists are located in a
       directory called white whithin the blacklist directory you specified
       with dbhome.
       Make sure that your white identifier is the first in the row of the pass
       directive. It must not have an exclamation mark in front (otherwise all
       entries belonging to white will be blocked, too).
    3. Initializing the blacklists
       Before you start up your squidGuard you should initialize the blacklists
       i.e. convert them from the textfiles to db files. Using the db format
       will speed up the checking and blocking.
       The initialization is performed by the following command:

       Initializing the b lacklists
squidGuard -C all
chown -R <squiduser> /usr/local/squidGuard/db/*

       The  second  command ensures that your squid is able to access the
       blacklists. Please for <squiduser> the uid of your squid.
       Depending on the size of your blacklists and the power of your computer
       this  may take a while. If anything is running fine you should see
       something like the following output in your logfile:

2006-01-29 12:16:14 [31977] squidGuard 1.2.0p2 started (1138533256.959)
2006-01-29 12:16:14 [31977] db update done
2006-01-29 12:16:14 [31977] squidGuard stopped (1138533374.571)

       If you look into the directories holding the files domains and urls you
       see that additional files have been created: domains.db and urls.db.
       These new files must not be empty!
       Only those files are converted you specified to block or whitelist in
       your squidGuard.conf file.

       Proceed with:     [8]Verify the configuration
                         [9]Extended Configuration of SquidGuard
       [10]Documentation
         _____________________________________________________________

       [11]Installation
         _____________________________________________________________

       Configuration

        [12]Getting started
        Destination ACLs
        Source ACLs
        [13]Redirect Rule
        [14]Time Constraints
        [15]Authentication
        [16]Regular Expressions
        [17]Examples
         _____________________________________________________________

       [18]Runtime Options
         _____________________________________________________________

       [19]About blocking
         _____________________________________________________________

       [20]Troubleshooting 
         _____________________________________________________________

       [21]Known Issues
         _____________________________________________________________

       [22]Other Sources
         _____________________________________________________________
       __________________________________________________________________

         © Powered by [23]Shalla Secure Services 2007-2008

References

   1. http://www.squidguard.org/index.html
   2. http://www.squidguard.org/download.html
   3. http://www.squidguard.org/Doc/
   4. http://www.squidguard.org/Devel/
   5. http://www.squidguard.org/blacklists.html
   6. http://www.squidguard.org/Contrib/
   7. http://www.squidguard.org/impressum.html
   8. http://www.squidguard.org/Doc/verify.html
   9. http://www.squidguard.org/Doc/extended.html
  10. http://www.squidguard.org/Doc/index.html
  11. http://www.squidguard.org/Doc/install.html
  12. http://www.squidguard.org/Doc/configure.html
  13. http://www.squidguard.org/Doc/redirect.html
  14. http://www.squidguard.org/Doc/extended.html#times
  15. http://www.squidguard.org/Doc/authentication.html
  16. http://www.squidguard.org/Doc/expressionlist.html
  17. http://www.squidguard.org/Doc/examples.html
  18. http://www.squidguard.org/Doc/runtimeops.html
  19. http://www.squidguard.org/Doc/aboutblocking.html
  20. http://www.squidguard.org/Doc/troubleshoot.html
  21. http://www.squidguard.org/Doc/known_issues.html
  22. http://www.squidguard.org/Doc/other_sources.html
  23. http://www.shalla.de/
