e2g as white list filter
322 views
Skip to first unread message
Mike Kai
Aug 19, 2014, 1:54:18 PM8/19/14
to e2gua...@googlegroups.com
We have e2g setup on 2 servers as normal "black list" filtering and it is working great.
We have another that currently has dansguardian setup as a white list (and has for over 7 years), but I know there are enough changes between dg and e2g that there may be a better way to use the white list option for better filtering.
In e2g, when used as a strict white list filter, how are greysitelist and exceptionsitelist handled? We have found that in dg, when on the greysitelist, some inappropriate material still gets through and we would like to avoid that. Any help on this subject would be appreciated.
Mike
We have another that currently has dansguardian setup as a white list (and has for over 7 years), but I know there are enough changes between dg and e2g that there may be a better way to use the white list option for better filtering.
In e2g, when used as a strict white list filter, how are greysitelist and exceptionsitelist handled? We have found that in dg, when on the greysitelist, some inappropriate material still gets through and we would like to avoid that. Any help on this subject would be appreciated.
Mike
Philip Pearce
Aug 27, 2014, 6:47:14 AM8/27/14
to Mike Kai, e2gua...@googlegroups.com
Mike,
There is some information on some logic changes in the e2guardian.release file.
Normally, if you want strict white list filter then you would put the sites you want allowed into exceptionsitelist and exceptionurllist, set blanket block in bannedsitelist, and leave greysitelist and greyurllist empty - same as dg. In this set-up no content checking is done, just url checking.
If you put urls in grey lists those sites will be content checked. The effectiveness of content checking depends on what phraselists you have active and how well you have tuned these to your requirements.
One change in E2G is that in DG https sites that were in the greysitelist would be allowed through without any content checking, whereas in E2G the greysitelist is not consulted when a https site is requested so only exceptionsites https sites are allowed in blanket block mode.
E2G should have the options you need to set up the filtering in any way you require, and if this is on a single network then you are able to do this with one server for different groups of users by defining filtergroups with different levels of access.
There is some information on some logic changes in the e2guardian.release file.
Normally, if you want strict white list filter then you would put the sites you want allowed into exceptionsitelist and exceptionurllist, set blanket block in bannedsitelist, and leave greysitelist and greyurllist empty - same as dg. In this set-up no content checking is done, just url checking.
If you put urls in grey lists those sites will be content checked. The effectiveness of content checking depends on what phraselists you have active and how well you have tuned these to your requirements.
One change in E2G is that in DG https sites that were in the greysitelist would be allowed through without any content checking, whereas in E2G the greysitelist is not consulted when a https site is requested so only exceptionsites https sites are allowed in blanket block mode.
E2G should have the options you need to set up the filtering in any way you require, and if this is on a single network then you are able to do this with one server for different groups of users by defining filtergroups with different levels of access.
Regards
Philip
Philip
--
You received this message because you are subscribed to the Google Groups "e2guardian" group.
To unsubscribe from this group and stop receiving emails from it, send an email to e2guardian+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages