OpenDNS Forums
The official support and discussion site of OpenDNS
Support
K-12 Forums
Categories
- Administrative
- Adult site blocking
- DNS-O-Matic / dynamic IPs
- Domain blocking
- Domain Name System (DNS) troubles
- Mobile instructions
- OpenDNS services
- Proxies, accelerators, and more
- Router instructions
- Satellite
- Shortcuts
- Wishlists and feature requests
-
Feeds
Vanilla 1.1.4 is a product of Lussumo. More Information: Documentation, Community Support.
This discussion has been inactive for longer than 30 days, and is thus closed.
-
I have just started using Google Chrome as my principal browser (Mac version). My question is this: Is there anything special I need to do to configure Chrome to work with Open DNS? For example, in the Preferences I am given the following options:
* Use a web service to help resolve navigation errors
* Use a prediction service to help complete searches and URLs typed in the address bar
* Predict network actions to improve page load performance
* Enable phishing and malware protection
At the moment I have disabled all of the above except the phishing and malware protection. Should all of the above be disabled or may I enable one or more of them without compromising or affecting my Open DNS service? TIA. -
From my experience they don't interfere with OpenDNS. I've all of them enabled and OpenDNS works as it should.
OpenDNS does offer Malware/botnet protection, phishing protection, as well as, domain-typo corrections and smartcache. These settings are found under "Dashboard --> Settings"
So you have the option to have not only OpenDNS protecting you but also Google. -
"At the moment I have disabled all of the above except the phishing and malware protection."
This would be my recommendation too, at least for the Windows version, after what has been reported here already.
See e.g. http://forums.opendns.com/comments.php?DiscussionID=14078 -
- CommentAuthormaintenance
- CommentTimeMay 21st 2012
I can't imagine why anyone would ever want prefetching/prediction enabled anyway. -
«Quote»
According to technical details Google published Tuesday, Pinkie Pie's odyssey began by exploiting a bug in a prerendering engine that helps Chrome work faster by gathering clues about webpages before they're loaded.
---
Anatomy of a hack: 6 separate bugs needed to bring down Google browser (Updated) | Ars Technica
http://arstechnica.com/security/2012/05/anatomy-of-a-hack-6-separate-bugs-needed-to-bring-down-google-browser/
«/Quote»
I'm no expert but I would assume that those, like me, who had one or a combination of the google chrome options discussed here were vulnerable to such complex hack.
Anyways, basically I'm just agreeing with maintenance, as well as, telling myself why enable those features in the first place. :| -
"why enable those features in the first place."
I'm afraid they are enabled by default, and users tend to not change defaults... -
- CommentAuthormaintenance
- CommentTimeMay 26th 2012
Aye, you have to disable them. At least you can disable them in a GUI setting in browsers like Chrome and SeaMonkey, unlike FireFox.
1 to 7 of 7
This discussion has been inactive for longer than 30 days, and is thus closed.