Hi,

first thanx to Rick Matthews and Nick Barron for your replies to my
questions. Unfortunately my email account got deleted and I couldn't get
some of the emails, but I found them in the mailing list archive. Still,
some things are unclear. Mr. Matthews, you write:

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/


So this works only in the domains blacklist? If I insert bad.com into
the URLs blacklist, only bad.com is blacklisted, but not
whatever.bad.com . So if I want to blacklist all virtual (second level)
domains, like whatever. bad.com, then I have to insert bad.com into the
domains blacklist rather than the urls blacklist?

Mr. Barron, you write:

now I have an "sgrebuild"
script that does a squidguard -C all followed by a chown -R squid.squid
/data/squidguard (adjust for your local install). That way if things are
behaving strangely you can run sgrebuild to make sure it's not a silly
mistake (my standard one is creating a new group as root and then
running
squidguard to reconfigure).

What is this sgrebuild? What I actually need, is something equivalent to
a windows bat file, where I can put :

Squidguard -C all
Squid -k reconfigure , and then it should be executed by clicking on
this file (or on a symbolic link to this file) from the kde environment,
otherwise I have to type in these lines in a console, in order to update
squid and squidguard after inserting a new url/domain into the
blacklists.

Regards,
Gert

Reply via email to