Difference between revisions of "SquidGuard"
m (Update how to see status of dag repositories.) |
Unnilennium (talk | contribs) |
||
| (6 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| + | {{Warning box|this content is outdated, and while there is some interesting feature in this contrib, you can find a more recently maintained contrib called [[WebFilter]] using squidguard with a panel available.}} | ||
| + | |||
===SquidGuard=== | ===SquidGuard=== | ||
| Line 5: | Line 7: | ||
J Bennett has packaged squidguard into a sme server compatible application. | J Bennett has packaged squidguard into a sme server compatible application. | ||
| − | If you have not installed the Dag repository please follow this instruction. | + | If you have not installed the Dag repository please follow this instruction.<br /> |
| − | + | ||
| + | You need to activate the [[Dag]] reposity before installing this contrib.<br /> | ||
| + | |||
| + | see [[dag|dag repository]] <br /> | ||
| + | |||
Download smeserver-squidguard-1.0-34.noarch.rpm to a folder on your sme server | Download smeserver-squidguard-1.0-34.noarch.rpm to a folder on your sme server | ||
| Line 17: | Line 23: | ||
That should install the correct package and any dependency rpms it requires. You must have the dag repository configured on your sme server (with status=disabled). You can see the status with this command. | That should install the correct package and any dependency rpms it requires. You must have the dag repository configured on your sme server (with status=disabled). You can see the status with this command. | ||
db yum_repositories show dag | db yum_repositories show dag | ||
| + | |||
| + | If you run this command the resulting output should look like: | ||
| + | dag=repository | ||
| + | BaseURL=http://apt.sw.be/redhat/el5/en/$basearch/dag | ||
| + | EnableGroups=no | ||
| + | Exclude=freetype,htop,iptraf,rsync,syslinux | ||
| + | GPGCheck=yes | ||
| + | GPGKey=http://dag.wieers.com/packages/RPM-GPG-KEY.dag.txt | ||
| + | Name=Dag - EL5 | ||
| + | Visible=no | ||
| + | status=disabled | ||
After installing the packages you must do | After installing the packages you must do | ||
| Line 23: | Line 40: | ||
This will restart your server. The web interface will not work if you fail to do the above commands. | This will restart your server. The web interface will not work if you fail to do the above commands. | ||
| − | + | Once you log into the server manager panel a new menu item will have been added with a main heading of JohnBennettServices with a sub topic Content Filtering. Click here to administer and fine tune Squidguard. | |
| + | |||
| + | There is a DB command to configure the blacklist. | ||
The default blacklist location is http://ftp.ost.eltele.no/pub/www/proxy/squidGuard/contrib/blacklists.tar.gz | The default blacklist location is http://ftp.ost.eltele.no/pub/www/proxy/squidGuard/contrib/blacklists.tar.gz | ||
| − | If you wish to change the default blacklist to something else | + | If you would like to confirm the the current blacklist site used. |
| + | config show squidguard | ||
| + | |||
| + | Currently the install above installs a blacklist site that does not seem to be active. So you might want to investigate another blacklist site, than the default one that is installed. If you wish to change the default blacklist to something else for example, use a command like this. | ||
| − | |||
config setprop squidguard Blacklist http://www.shallalist.de/Downloads/shallalist.tar.gz | config setprop squidguard Blacklist http://www.shallalist.de/Downloads/shallalist.tar.gz | ||
| Line 63: | Line 84: | ||
---- | ---- | ||
| − | |||
[[Category:Administration:Content Spam Virus Blocking]] | [[Category:Administration:Content Spam Virus Blocking]] | ||
| + | [[Category:Contrib:webfiltering]] | ||
| + | [[Category:Deprecated Contrib]] | ||
Latest revision as of 03:46, 27 May 2022
SquidGuard
smeserver packaged version
J Bennett has packaged squidguard into a sme server compatible application.
If you have not installed the Dag repository please follow this instruction.
You need to activate the Dag reposity before installing this contrib.
see dag repository
Download smeserver-squidguard-1.0-34.noarch.rpm to a folder on your sme server
wget http://mirror.contribs.org/contribs/jbennett/sme7/squidguard/RPMS/smeserver-squidguard-1.0-35.noarch.rpm
cd to the folder on your sme server where smeserver-squidguard is located and do
yum localinstall smeserver-squidguard*.rpm --enablerepo=dag
That should install the correct package and any dependency rpms it requires. You must have the dag repository configured on your sme server (with status=disabled). You can see the status with this command.
db yum_repositories show dag
If you run this command the resulting output should look like:
dag=repository BaseURL=http://apt.sw.be/redhat/el5/en/$basearch/dag EnableGroups=no Exclude=freetype,htop,iptraf,rsync,syslinux GPGCheck=yes GPGKey=http://dag.wieers.com/packages/RPM-GPG-KEY.dag.txt Name=Dag - EL5 Visible=no status=disabled
After installing the packages you must do
signal-event post-upgrade signal-event reboot
This will restart your server. The web interface will not work if you fail to do the above commands.
Once you log into the server manager panel a new menu item will have been added with a main heading of JohnBennettServices with a sub topic Content Filtering. Click here to administer and fine tune Squidguard.
There is a DB command to configure the blacklist. The default blacklist location is http://ftp.ost.eltele.no/pub/www/proxy/squidGuard/contrib/blacklists.tar.gz
If you would like to confirm the the current blacklist site used.
config show squidguard
Currently the install above installs a blacklist site that does not seem to be active. So you might want to investigate another blacklist site, than the default one that is installed. If you wish to change the default blacklist to something else for example, use a command like this.
config setprop squidguard Blacklist http://www.shallalist.de/Downloads/shallalist.tar.gz
The supdate script will convert the lists to *.db files which load a lot faster when stopping and starting squidguard.
Use the content filtering panel in server-manager, to add entries. You have trusted and untrusted (domains, urls, expressions). Add your entries, then restart squid with
/etc/rc7.d/S90squid stop /etc/rc7.d/S90squid start
You will know when things are ready when you see this in the /var/log/squidguard/squidguard.log file:
2007-03-18 17:14:54 [3687] squidGuard 1.2.0 started (1174256093.054)
2007-03-18 17:14:54 [3687] squidGuard ready for requests (1174256094.968)
See advice of mrjhb3 here:
http://forums.contribs.org/index.php?topic=36217.msg160088#msg160088
Previous version package information
Information about a previous version of squidguard is here:
URL redirector used to use blacklists with the proxysoftware Squid.
Mini Howto: http://forums.contribs.org/index.php?topic=34337.msg151745#msg151745
References
Squidguard Homepage: http://www.squidguard.org/
