Difference between revisions of "SquidGuard"

From SME Server
Jump to navigationJump to search
m
Line 9: Line 9:
  
 
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
  wget http://mirror.contribs.org/contribs/jbennett/sme7/squidguard/RPMS/smeserver-squidguard-1.0-34.noarch.rpm  
+
  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
 
cd to the folder on your sme server where smeserver-squidguard is located and do

Revision as of 01:54, 2 November 2011

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.

The following command will configure the Dag repository on SME Server. EDIT NOT COMPLETE!


To create an entry in the database for the epel repository we open put the following commands in a terminal window or in a shell window:

/sbin/e-smith/db yum_repositories set epel repository \

Name 'SME Server - epel' \
BaseURL 'http://<http://download.fedoraproject.org/pub/epel/7/$basearch' \
EnableGroups yes \
GPGCheck yes \
Visible no \
status disabled

To enable the changes:

    signal-event yum-modify

Just to be sure, give yum a fresh start:

    yum clean all

After adding it to the database we have to update the changes to the configuration file:

signal-event yum-modify

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).

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.

Then use the server manager panel to control it all. 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 wish to change the default blacklist to something else do (for example)

config show squidguard
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/