SquidGuard package TEST

dhipo

more /usr/local/etc/squidGuard/squidGuard.conf

============================================================

SquidGuard configuration file

This file generated automaticly with SquidGuard configurator

(C)2006 Serg Dvoriancev

email: dv_serg@mail.ru

============================================================

logdir /var/squidGuard/log
dbhome /var/db/squidGuard

Todas as lojas (users in branchoffice)

src lojas {
ip 192.168.0.0/255.255.0.0
log block.log
}

Todos do Escritorio Central (users in HeadOffice)

src EC {
ip 100.0.2.0/16
log block.log
}

Acesso especial (special access users)

src especiais_loja {
ip 192.168.11.98
ip 192.168.37.32
ip 192.168.38.12
log block.log
}

Acesso sem limites (without limits users)

src super-users {
ip 100.0.0.1
ip 100.0.0.195
ip 100.0.2.40
log block.log
}

dest ads {
domainlist ads/domains
urllist ads/urls
log block.log
}

dest aggressive {
domainlist aggressive/domains
urllist aggressive/urls
log block.log
}

dest audio-video {
domainlist audio-video/domains
urllist audio-video/urls
log block.log
}

dest drugs {
domainlist drugs/domains
urllist drugs/urls
log block.log
}

dest gambling {
domainlist gambling/domains
urllist gambling/urls
log block.log
}

dest hacking {
domainlist hacking/domains
urllist hacking/urls
log block.log
}

dest mail {
domainlist mail/domains
log block.log
}

dest porn {
domainlist porn/domains
expressionlist porn/expressions
urllist porn/urls
log block.log
}

dest proxy {
domainlist proxy/domains
urllist proxy/urls
log block.log
}

dest redirector {
domainlist redirector/domains
urllist redirector/urls
log block.log
}

dest spyware {
domainlist spyware/domains
urllist spyware/urls
log block.log
}

dest suspect {
domainlist suspect/domains
urllist suspect/urls
log block.log
}

dest violence {
domainlist violence/domains
expressionlist violence/expressions
urllist violence/urls
log block.log
}

dest warez {
domainlist warez/domains
urllist warez/urls
log block.log
}

Lista Negra Leo (our black list)

dest ListaNegra {
domainlist ListaNegra/domains
expressionlist ListaNegra/expressions
urllist ListaNegra/urls
log block.log
}

Lista de Sites Liberados (our white list)

dest ListaBranca {
domainlist ListaBranca/domains
expressionlist ListaBranca/expressions
urllist ListaBranca/urls
}

Sites liberados para lojas (free sites to branchoffice users)

dest permitidosLoja {
domainlist permitidosLoja/domains
log block.log
}

Sites Liberados para EC (free sites to HeadOffice)

dest permitidosEC {
domainlist permitidosEC/domains
log block.log
}

acl {
# Lista de Lojas Liberadas
lojas {
pass ListaBranca permitidosLoja none
}

# permitidos EC
EC {
pass ListaBranca permitidosEC none
}

# usuarios controlados com acesso total
especiais_loja {
pass !ads !aggressive !audio-video !drugs !gambling !hacking !m
ail !porn !proxy !redirector !spyware !suspect !violence !warez !ListaNegra all
}

# Super usuarios
super-users {
pass all
}
default {
pass ListaBranca none
redirect http://127.0.0.1/sgerror.php
}
}

dvserg

Make this for testing

disable all ACL's (checkbox on every acl)
uncheck all items on Default rule and set !all (deny all) - test this for block all traffic
enable ListaBranca in default and test acces to him and no-access for other
one by one enable ACLS and test him for access (first enable you special acls)

You need find what ACL wrong configured.

PS after any change before test press Apply button and see Servise string for green (in latest version SG)(mean - SG success started) below Apply button

dvserg

2 mantunespb

installed to put happened this error in the end of the site is the same not initiated

Warning: fopen(/usr/local/etc/squidGuard/squidguard_conf.xml): failed to open stream: No such file or directory in /etc/inc/pfsense-utils.inc on line 1094 Warning: fwrite(): supplied argument is not a valid stream resource in /etc/inc/pfsense-utils.inc on line 1095 Warning: fclose(): supplied argument is not a valid stream resource in /etc/inc/pfsense-utils.inc on line 1096 Warning: fopen(/usr/local/etc/squidGuard/squidguard_conf.xml): failed to open stream: No such file or directory in /etc/inc/pfsense-utils.inc on line 1094 Warning: fwrite(): supplied argument is not a valid stream resource in /etc/inc/pfsense-utils.inc on line 1095 Warning: fclose(): supplied argument is not a valid stream resource in /etc/inc/pfsense-utils.inc on line 1096

Several questions

do you have installed squidGuard port before installation package? (must be deinstalled)
check /usr/local/etc/squidGuard/ path for exists

dhipo

ok /// i do this and satyed strange… but i found an tip ... andnow evething is working... we need compile the lists (blacklists ,destinations, etc) every time what anything is added or removed from blacklists or destinations... the command is ... to first time :
/usr/local/bin/squidGuard -c /usr/local/etc/squidGuard/squidGuard.conf -C all -d

or to updates

/usr/local/bin/squidGuard -c /usr/local/etc/squidGuard/squidGuard.conf -u -d

the acls are working now
....

dvserg

<english problem="">I have understood that there is problems with(since) rebuilding db?
Blacklist db rebuild once after his downloading and installation
User db may be processed with each pressing by button 'Apply'
(user db each time created as new but not diff)

Please post you detail ussues - where problem?

ps i will have test too</english>

dhipo

ok …. i will try be clear ..... on press apply button or save new Destinations is not creating the db files..
i created manually using the comand
/usr/local/bin/squidguard -c /usr/local/etc/squidGuard/squidGuard.conf -C all

but every time , when a new url ,expression or domain is added to destinations is necessary run the command
/usr/local/bin/squidguard -c /usr/local/etc/squidGuard/squidGuard.conf -d

if db files was not created manually the rules (ACLS) does not work ..
but, after db creation (manually) works fast and was expected..

dhipo

new doubt …
Can i have an acl like this

" pass MyList "

without the ' !all ' at the end of line ?

dvserg

@dhipo:

new doubt …
Can i have an acl like this

" pass MyList "

without the ' !all ' at the end of line ?

I test bug with db nearest time ???

About ACL
'!all' convert to config as 'none'
This is default rule for current ACL
'pass MyList all' mean pass 'MyList' and 'all' - passed all
pass MyList !sex all - mean pass MyList all and deny sex
pass MyList none (equiqalence !all) - mean pass only MyList and deny all other

dvserg

Rename wisout .txt, replace on '/usr/local/pkg' this and test it.

squidguard_configurator.inc.txt

dhipo

ok … i changed the squidguard_configurator file ... works good... an new discovered tip .... ACL order is too important .. look this :

acl 1 source is 192.168.1.0/24 "pass mylist none" -- my list have only some permited sites

acl2 source is 192.168.1.20 pass all

in this case acl2 never is used

but if acl2 is in top order works like desired....

can an option to move order in acls added ???

dvserg

@dhipo:

ok … i changed the squidguard_configurator file ... works good... an new discovered tip .... ACL order is too important .. look this :

acl 1 source is 192.168.1.0/24 "pass mylist none" -- my list have only some permited sites

acl2 source is 192.168.1.20 pass all

in this case acl2 never is used

but if acl2 is in top order works like desired....

can an option to move order in acls added ???

Great test!! I missed this moment and this very serious. I will work about this :-[

dvserg

Do you have url's with information about squidGuard ALC's order?

dhipo

no i don't found anything about acl order on internet …. but it's a try an error what i did ....

look ...

i thin in this moment we can do an ACL tester .... to show what ACL is being applied ....

on command line the test is ....

echo "http://www.example.com 100.0.2.10/ - - GET" | /usr/local/bin/squidGuard -c /usr/local/etc/squidGuard/squidGuard.conf -d

and will reply on last lines

2007-06-24 10:54:39 [15031] squidGuard 1.2.0 started (1182693279.170)
2007-06-24 10:54:39 [15031] squidGuard ready for requests (1182693279.178)
2007-06-24 10:54:39 [15031] Request(EC/none/-) http://www.example.com 100.0.2.10/- - -
http://127.0.0.1/sgerror.php?url=403 100.0.2.10/- - -
2007-06-24 10:54:39 [15031] squidGuard stopped (1182693279.178)

look the acl NAME there Request(EC/none/-)

look this … the ip tested down is an user with special access, but with porn denied

echo "http://www.sex.com 192.168.19.97/ - - GET" | /usr/local/bin/squidGuard -c /usr/local/etc/squidGuard/squidGuard.conf -d

reply 2007-06-24 10:59:26 [15573] squidGuard ready for requests (1182693566.468)
2007-06-24 10:59:26 [15573] Request(especiais/porn/-) http://www.sex.com 192.168.19.97/- - -
http://127.0.0.1/sgerror.php?url=403 192.168.19.97/- - -
2007-06-24 10:59:26 [15573] squidGuard stopped (1182693566.469)

and now the full network range … with limited access...

echo "http://www.sex.com 192.168.0.0/ - - GET" | /usr/local/bin/squidGuard -c /usr/local/etc/squidGuard/squidGuard.conf -d

look the different acl 2007-06-24 11:04:25 [16181] Request(lojas/none/-) http://www.sex.com 192.168.0.0/- - -
http://127.0.0.1/sgerror.php?url=403 192.168.0.0/- - -
2007-06-24 11:04:25 [16181] squidGuard stopped (1182693865.587)

in my testings i discovered :
if an ACL with specific ip ( host address eg: 192.168.19.97 ) is after of a network range … the acl is never processed ..

then i suggest and button to move acl order like rules order in pfsense ...

dvserg

http://www.sdconsult.no/linux/SquidGuard/doc.html

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.

May be source order have effect? Analyze pls this url.. (my translator give stuppid text)

dhipo

is this ….

The order of "ACL" is important ...
look this note:

Note: The client groups are matched in the order they are defined.

we need an control to ordering "ACL"s

dvserg

@dhipo:

is this ….
The order of "ACL" is important ...
look this note:
Note: The client groups are matched in the order they are defined.
we need an control to ordering "ACL"s

Client group this is Sources blocks
Do you have possible test config with swithching sources blocks? (manually swap and restart squid). I will be able to test tomorrow :-\

dhipo

no …. source or destinations order is NOT important ....

important is the ACL order .... blocking is made based on order of ACL...

dhipo

i did test order of acl and this is real …. .ACL order is important...

dvserg

@dhipo:

i did test order of acl and this is real …. .ACL order is important...

I now have test via remote access on my work next simple config


src_myip_on = myip
src_myip_off = myip

acl {
  default .... none // all block
  src_myip_on ... all // all pass
  src_myip_off ... none //all block
}

–- A --- beginner
sources (1)src_myip_on (2)src_myip_off
ACLS (1)default (2)src_myip_on (3)src_myip_off
result MyIP Access = pass

--- B --- swapping acls
sources (1)src_myip_on (2)src_myip_off
ACLS (1)default (2)src_myip_off (3)src_myip_on
result MyIP Access = pass (!!)

-- C -- swapping sources
sources (1)src_myip_off (2)src_myip_on
ACLS (1)default (2)src_myip_on (3)src_myip_off
result MyIP Access = blocked (!!)

dhipo

you are right ….. the sources order change the result of policy .... i hate this.... only about lucky .... but my order of sources was right and when i changed policies stop to work.....

great work ..... SOURCES MUST BE ORDERED TO WORK ....