I've been trying to stay out of this discussion to let those more
knowledgeable about
squidguard take the reigns, however I feel some folks are overcomplicating
the issue.
I'm observing a working squid.conf file (I left most defaults as they were)
indeed heirarchy_stop cgi_bin ?
should be
hierarchy_stoplist cgi-bin ?
or so says my squid.conf
# the default squid.conf will work with squidguard changing but a few
parameters.
# first, which you did
redirect_program /usr/sbin/squidGuard -c /etc/squidGuard.conf
#then the number of squidguard processes squid should start (this may
default to 5 if not set)
redirect_children 4
# comment this out altogether (default is to send all requests to the
redirector)
# redirector_access
# your http_access concerns me, in that there is no need to provide cache
access to anyone
# but your local net in most cases.
# here I have an acl which defines my LAN and allow it.. and then my
catch-all rule for
# everything else
acl lanhosts src 10.137.217.0/255.255.255.0
http_access allow lanhosts
http_access deny all
other than that, if you have no other special tweaking that you want to do
with squid the
defaults should be fine.
as far as squidGuard.conf
logdir /var/log/squid
dbhome /var/lib/squidGuard/blacklists
dest porn {
domainlist porn/domains
urllist porn/urls
}
acl {
default {
pass !porn all
redirect http://www.yourhost.com/denied.htm
}
}
would do the trick.
P.S.: This list may not be about configuring squid but it is very much about
getting
squidGuard to work WITH squid. Pointing someone to the squid lists with a
squidGuard
problem is just being lazy.. If you do not have time for the questions, do
not answer
them. This is not bugtraq, people come here for help.
