Florin wrote: > Hello, > > >>I think I know *why* keywords (expressions) don't work quite >>as expected. squid guard apparently checks only the *first* >>word in the keyword list provided by a web page. If the >>*first keyword* matches anything in the expression list then >>the page is rejected. If the first keyword is not matched >>then the page is let through even though there might be >>additional keywords provided that would match the list. >> >>For example: >> >> >>using www.linux-mandrake.com/en as an example. configure >>the expressions file in >>/usr/share/squidGuard-1.2.0/db/banneddestination/expressions >>with just (download) >> >>restart squid and load the page back up. The page is >>accepted, even though download is in the expression list. >>Hmm not good. Now if you change the expresions to (linux) >>or just add linux to the list and restart squid the page >>will be rejected, because the first keyword on the page is >>linux. >> >>This looks like a defect if you ask me... >> >>-randy > > > as I said, this is because of the > /usr/share/squidGuard-1.2.0/banneddestination/*.db files > > Indeed, the snf frontend modifications are present only in the plain text > files and not in the db files. Remove the db files or run squidGuard with > a -C command to recreate the db files ... or >
I removed the db files. I have no dbfiles in /usr/share/squidGuard-1.2.0/db/banneddestination/ I removed those at your first suggestion. > wait for the latest squidGuard package (I won't create the db files in > post for the SNF sections). I will upload it ASAP. I will snare it ( i'm in the process of updating my cooker directory now ). -randy
