Sep 26 05 4:18 pm
Nov 17 07 5:29 pm
Nov 18 07 3:27 am
ggiebler wrote:
2. There are a number of sights which can allow users to bypass the content filters, e.g., https://www.megaproxy.com. Is there a way to prohibit users from using such sights. Putting megaproxy in the ban list does not prevent users from going to that sight since it begins with https://.
ggiebler wrote:3. I'm having trouble getting the hosts file to work under the DNS/WINS Resolver configuration. I was thinking this might be a good way to ban a number of sights more easily than adding them to PureSight's or WWW Proxy Server's or System Policy's ban lists. I have all clients set up as assumed users based on IP address. No clients are using the Wingate client. Everyone connects via NAT. DHCP is disabled. All clients have fixed IP addresses. Is there something I need to do to get the hosts file to work?
Nov 22 07 3:21 pm
ggiebler wrote:1. Some forbidden Web pages filtered by PureSight will load if you keep refreshing your browser. For example, I have the Sex filter in PureSight set to 10% certainty. Any lower than that, and it seems that too many legitimate sites get blocked. If I try to load playboy.com, it initially gets rejected by PureSight as having a very high likelihood of containing prohibited content (86%). Subsequent refreshings of the browser result in its being rejected, but with ever lower likelihoods of containing prohibited content, until finally it does in fact load in the browser.
Nov 22 07 9:40 pm
Nov 28 07 4:31 am
adrien wrote:Hi
We'll have to look into this further, thanks for raising it again.
PureSight 2 has a list of sites that are pre-classified, and I'm surprised that the sites mentioned aren't on the list, which should therefore provide a consistent rejection.
Or are you getting percentages reported back?
Regards
Adrien
Dec 07 07 4:19 am