Koozali.org: home of the SME Server
Obsolete Releases => SME 7.x Contribs => Topic started by: bcliburn on October 21, 2006, 07:27:55 AM
-
I ran a yum upgrade and it updated my dansguardian and now all of my settings are fricked. Anyone else have this happen yet?
-
The changes between 2.8 and 2.9 are substantial
The recommendation from the dansguardian mailing list is to begin editing the new lists rather than try to edit your old ones
the new dans runs out of the box,
but you probably have to edit at least
/etc/dansguardian/dansguardian.conf
/etc/dansguardian/dansguardianf1(f2,fn).conf
group filter files are kept in
/etc/dansguardian/lists/fn/*
I suggest you also update smeserver-dansguardian, but it's optional
http://www.dungog.net/sme/changelog/index.php
http://www.dungog.net/sme/dansguardian.php
As dansguardian is likely to be updated regularly now it's out of alpha
I've revised our repo setup instructions for gpl users
Method 2.
as suggested at contribs.org, documentation for 3rd party repositories
is to add the repo with status disabled
http://no.longer.valid/phpwiki/index.php/3rdPartyYumRepositories
then you install or check for updates with. eg.
yum --enable-repo=dungog --enable-repo=dungogMembers smeserver-sarg
yum --enable-repo=dungog list updates
you may also wish to update some rpms from a repo but not others eg.
exclude 'dansguardian smeserver-dansguardian'
the new command to setup this method is now
db yum_repositories set dungog repository \
BaseURL http://sme.dungog.net/packages/smeserver/7.0/i386/dungog/ \
EnableGroups yes \
GPGCheck no \
Name 'SME Server 7 - dungog' \
Visible yes \
exclude 'dansguardian smeserver-dansguardian'
status disabled
/sbin/e-smith/expand-template /etc/yum.conf
-
I ran a yum upgrade and it updated my dansguardian and now all of my settings are fricked. Anyone else have this happen yet?
Yes, luckily it saved a backup copy of the original files so I was able to do some copy/paste work to get my customized block template back. It did take a little digging to get the rest of my settings set again...
I was surprised to see that the server sent me an email saying that updates where available and that it was for Dansguardian...
Ryan
-
I got it all working fine now again except the ident client I was using I can't get that to work now.
-
The changes between 2.8 and 2.9 are substantial
The recommendation from the dansguardian mailing list is to begin editing the new lists rather than try to edit your old ones
the new dans runs out of the box,
but you probably have to edit at least
/etc/dansguardian/dansguardian.conf
/etc/dansguardian/dansguardianf1(f2,fn).conf
group filter files are kept in
/etc/dansguardian/lists/fn/*
Everyone is saying that you must configure the dansguardian.conf file but what must we put in it? Is there a sample or something?
-
It will run and work as soon as you install it, there are things that should be changed such as;
# Web Access Denied Reporting (does not affect logging)
#
# -1 = log, but do not block - Stealth mode
# 0 = just say 'Access Denied'
# 1 = report why but not what denied phrase
# 2 = report fully
# 3 = use HTML template file (accessdeniedaddress ignored) - recommended
#
reportinglevel = 2
And
# accessdeniedaddress is the address of your web server to which the cgi
# dansguardian reporting script was copied. Only used in reporting levels 1 and 2.
#
# This webserver must be either:
# 1. Non-proxied. Either a machine on the local network, or listed as an exception
# in your browser's proxy configuration.
# 2. Added to the exceptionsitelist. Option 1 is preferable; this option is
# only for users using both transparent proxying and a non-local server
# to host this script.
#
# Individual filter groups can override this setting in their own configuration.
#
accessdeniedaddress = 'http://yourdomain/cgi-bin/dansguardian.pl'
But it should still work even if you don't change that.
Just make sure you point your web browsers to the SME box as a proxy server.