tag:blogger.com,1999:blog-13777170.post6277844477820339254..comments2024-03-11T02:35:50.848-05:00Comments on grand stream dreams: AVG Free Version 8 (post-SP1) – Definitely Different!Unknownnoreply@blogger.comBlogger2125tag:blogger.com,1999:blog-13777170.post-5070906842801128852008-07-07T18:03:00.000-05:002008-07-07T18:03:00.000-05:00@ Anonymous - Thanks for the comment. I appreciat...@ Anonymous - Thanks for the comment. I appreciate it.<BR/><BR/>I don't think I actually made a statement in this post about "what" LinkScanner was actually doing (DNS lookups now versus the prior prefetching behavior).<BR/><BR/>What I was trying to capture in the measurements is that this new "method" of LinkScanner behavior seems to be much less burdensome on the local user's browsing experience...assuming they have done a default install of AVG Free 8...than in the pre 138 build releases (which was horrible!).<BR/><BR/>I'm not defending AVG's LinkScanner product here at all. In fact, I <A HREF="http://grandstreamdreams.blogspot.com/2008/06/remove-linkscanner-from-avg-simply.html" REL="nofollow">still recommend doing a custom install and leaving it off</A>...and using some other methods for more secure web-browsing and poisoned URL avoidance.<BR/><BR/>I still think LinkScanner has a long way to go, or that AVG should pull it entirely until they come up with a better solution that helps the user but doesn't hurt either the web-masters/bandwidth/DNS lookup sources. As you pointed out, the DNS folks are the next group that should raise the alarms.<BR/><BR/>I personally use <A HREF="http://www.opendns.com/" REL="nofollow">OpenDNS</A> for our home network configuration, set at the router level. Works great and provides a nice measure of seamless security protection against phishing sites. Coupled with Firefox 3.0's protection (+NoScript) and all the other piles of stuff (A/V, A/M, firewall, HIPS, etc.) I feel pretty secure on our home systems browsing the web. Don't really have a need for full real-time linkscanning while I browse.<BR/><BR/>While LinkScanner's new form is certainly "friendlier" I really doubt that it now provides much "protection" and web-surfing safety to even bother. Turned out to be a real debacle for AVG.<BR/><BR/>If I misunderstood your comment, please let me know.<BR/><BR/>-Cheers!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-13777170.post-11504116808077230422008-07-07T17:17:00.000-05:002008-07-07T17:17:00.000-05:00The 138 build isn't scanning websites the way you ...The 138 build isn't scanning websites the way you suggest. It's not even going to the websites listed in the search engine links. All it's doing is a DNS lookup on those URLs. When you mouseover the green checkmark, it says it scanned the site, and it shows the IP address it got from the DNS lookup and how many seconds it took, but it didn't go to the site itself. It's a trick. I suspect your local DNS provider isn't too happy about this.Anonymousnoreply@blogger.com