Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Chrome is blocking wired.com

wired.com

Post reply on HN
Print view View original

71–80 of 98 posts

Re: Chrome is blocking wired.com

#71

Post by Matt_Cutts »

pearjuice wrote: post #49

I can't believe on HN of all places people are using Chrome its malware-detecting-capabilities. Friendly reminder that EVERY REQUEST you make with it enabled, will be passed through Google its filters. You should turn all Google networking activities in your browser off. By default, there are at least five or so enabled which will happily send every request you make to Google. Some services even go as far as logging…

pearjuice, this simply isn't true. The way that Chrome does this is periodically downloads a file from Google. The file consists of hashes of known-dangerous web pages. When you visit a new URL, the URL is hashed locally and checked against the client-side list of hashes of known-bad pages. If there's no match, Chrome proceeds normally. Only if there is a hash collision does Chrome do more checking to see if the URL is safe.

Here's more information in case you want to read more: https://code.google.com/p/google-safe-browsing/wiki/SafeBrow...

Re: Chrome is blocking wired.com

#72

Post by larrys »

Matt_Cutts wrote: post #67
dpcan wrote: post #61

Earlier quoted context omitted.

Yes, but they still block websites that are not connected to Google Webmaster Tools, and the site owners may not realize it. It would be nice if they notified the domain registrant as a heads-up because most small biz site owners that find their way to me may have sites that were designed years ago that need little to no maintaining, so they don't know they've been blocked as they barely ever look at their own sites.

We explored trying to email whois contacts or standard addresses (such as webmaster@example.com or postmaster@example.com) and essentially got zero pickup. That's one of the reasons we provide Webmaster Tools, and so far it's our best channel to notify small business owners. We can sometimes label sites as hacked in the search results, but Webmaster Tools is definitely the preferred channel for communication of stuff…

"We explored trying to email whois contacts or standard addresses"

Ironic since the original reason for the tech contact was exactly to be notified for issues like this.

Would like to add that as a registrar though we get a reasonably good response to emails that we send. [1]

Perhaps there is something about getting an email from google that says "it's probably spam". Or any large well known company that is often the subject of spam attempts.

Even given that though it's hard for me to believe that the results were close to zero.

[1] We also find that when a domain is deleted for non payment the person frequently claims they received no email notice but then proceeds to make some reference to something that was on the email notice.

Re: Chrome is blocking wired.com

#73

Post by comex »

shortstuffsushi wrote: post #51
zurn wrote: post #38

Earlier quoted context omitted.

Exploiting programming errors in the browser is one way. Because browsers are written in very unsafe programming languages (C++), bugs are regularly exploitable so that by specially crafting the bug-triggering input data they can be fooled to scribble content-controlled data inside the browser's memory space. For example, a memory handling bug might let the page overwrite some of the browser's code with data coming f…

While some of the vectors you've mentioned could potentially be exploitable, blaming a "very unsafe programming language," isn't really a good explanation. These issues could occur in any program and any programming language -- it's not a problem specific to C languages.

Most(?) browser vulnerabilities are caused by errors in C++ code which would not be exploitable in memory safe languages. One of the goals of Mozilla's Servo is to write a browser that's memory safe without compromising performance.

Re: Chrome is blocking wired.com

#74

Post by [deleted] »

Matt_Cutts wrote: post #67
dpcan wrote: post #61

Earlier quoted context omitted.

Yes, but they still block websites that are not connected to Google Webmaster Tools, and the site owners may not realize it. It would be nice if they notified the domain registrant as a heads-up because most small biz site owners that find their way to me may have sites that were designed years ago that need little to no maintaining, so they don't know they've been blocked as they barely ever look at their own sites.

We explored trying to email whois contacts or standard addresses (such as webmaster@example.com or postmaster@example.com) and essentially got zero pickup. That's one of the reasons we provide Webmaster Tools, and so far it's our best channel to notify small business owners. We can sometimes label sites as hacked in the search results, but Webmaster Tools is definitely the preferred channel for communication of stuff…

[deleted]

Re: Chrome is blocking wired.com

#75

Post by lvs »

bashcoder wrote: post #62
lvs wrote: post #44

Earlier quoted context omitted.

First, it's already been unblocked. Second, this is what it says at the above link: --SNIP-- What happened when Google visited this site? Of the 26 pages we tested on the site over the past 90 days, 4 page(s) resulted in malicious software being downloaded and installed without user consent. The last time Google visited this site was on 2014-04-05, and the last time suspicious content was found on this site was on 20…

> First, it's already been unblocked. It's still blocked for me, with Google branding wired.com as "a known malware distributor."

Well that's technically a correct statement.

Try:

chrome://net-internals/#dns Click "Clear host cache"

Re: Chrome is blocking wired.com

#77

Post by nolok »

Istof wrote: post #66
fooyc wrote: post #63

Earlier quoted context omitted.

The browser has a local copy of the blocked sites database; so it doesn't have to do any extra request in order to check if a web site is blocked or not.

I didn't know that and I think that it is very surprising since Google usually doesn't turn down free information about it's users.

Why would they turn down the expected payment for their free services ? That would be stupid.

Re: Chrome is blocking wired.com

#79

Post by lukeschlather »

th3iedkid wrote: post #25
lukeschlather wrote: post #12

Weird: http://safebrowsing.clients.google.com/safebrowsing/diagnost... The page essentially says "We believe this page is suspicious, and we have no evidence to back up that claim." EDIT: They must have updated it/ busted a cache. The page is now reporting some evidence.

funny it says "Of the 20 pages we tested on the site over the past 90 days, 0 page(s) resulted in malicious software being downloaded and installed without user consent. The last time Google visited this site was on 2014-03-25, and suspicious content was never found on this site within the past 90 days." does zero count to be blocked?

Weird, I must have had a cached copy (which is really strange since Chrome was blocking Wired for me.)

Re: Chrome is blocking wired.com

#80

Post by fooyc »

Istof wrote: post #66
fooyc wrote: post #63

Earlier quoted context omitted.

The browser has a local copy of the blocked sites database; so it doesn't have to do any extra request in order to check if a web site is blocked or not.

I didn't know that and I think that it is very surprising since Google usually doesn't turn down free information about it's users.

I believe Chrome is much more strategical than that.

Google could lose enormous market share if any major browser decided to change the default search engine. So they created their own major browser.

Chrome is not an information source for Google, it's a way to maintain Google as a default search engine.

They fund Mozilla for the same reason.

Post reply on HN