Matador wrote:I have also been wrestling with this the past couple of days. It is definitely K9 that is hardcoding the IP addresses in the hosts file (used procmon to verify). This is causing all sorts of problems -- I can't even get to Google half of the time and Google Music can't log in, for example. Will a moderator please respond and let us know what's going on and how to fix this? Thanks!
dejal wrote:I've removed K9 from my machines until this is fixed.
I love the product.
the hosts file didn't work anymore. I want what I want in the hosts file, not what BC thinks I should have.
I'm also using Nortons Connect Safe https://dns.norton.com/dnsweb/faq.do
and I have it password protected on a E2000 router that was flashed with DD-WRT
K9 is a bit better in flagging "bad" sites.
jBCk9 wrote:These entries are from the k9 software and 188.8.131.52 is a google IP address. The IP 184.108.40.206 is a safe non-ssl IP address that google recommends that schools and the like point all http://www.google requests to, there is a google article on it if you do a search for "schools google encrypted" (sorry, I don't have the url handy). I believe k9 started using the hosts file to help combat ssl-encryption on google search a while back. As this is google's own recommended method for handling non-ssl searches, it should not adversely affect anything, all other google services should work as expected as the article states. If you are having problems or can't find a way to turn it off (sounds like you don't want this feature but can't find a way to disable it) then I would suggest contacting k9 support directly (see the sticky above). I have found them to very responsive and very helpful, and this will help others who might be having problems as well. They almost never respond to these boards.
My two cents, for parental controls dns solutions are a good backup but have way too many loopholes. Creative/knowledgable teens can get around them quite easily.
jBCk9 wrote:I agree, if you turn off "force safe search", expected behavior would be to remove the entries from the hosts file. You might be able to use encrypted.google.com, assuming "force safe search" is unchecked. Admiralty not a perfect solution, but you could probably configure the toolbar to use that url and might work pretty good until/if they change k9.
Well, it is free software so I can understand why they have limited resources on it, such as not dealing with the forums. But in my experience they do respond very quickly to support tickets. The fact that they do a great job maintaining it and that they address the ever changing nature of the internet is greatly appreciated.
To log a support ticket go to http://www1.k9webprotection.com/support/overview, select instant support, scroll to the bottom "my problem is not listed." You will need your license from http://127.0.0.1:2372/about
Matador wrote:I managed to keep it from overwriting the file by modifying the ACLs on the hosts file itself. Seems to be a doable workaround for now.
Take ownership of the file with your user account and give yourself explicit write permissions on it.
Then, remove write permissions from the Administrators group, leaving Read/Execute.
Users browsing this forum: No registered users and 3 guests