I'm a little confused how a webpage can infect a machine with malware? Is this typically through Java Applets/other plugins?
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…
Chrome is blocking wired.com
51–60 of 98 posts
Re: Chrome is blocking wired.com
#52I 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…
Re: Chrome is blocking wired.com
#53So when does robot slander/libel suits begin? I'd be mighty ticked if google started labelling my sites as malware when they're clearly not.
Re: Chrome is blocking wired.com
#54So when does robot slander/libel suits begin? I'd be mighty ticked if google started labelling my sites as malware when they're clearly not.
Re: Chrome is blocking wired.com
#55Re: Chrome is blocking wired.com
#56If they leave their WordPress un-patched, or have a crappy plugin installed with security holes, or their FTP info is guessed, etc, hackers drop some malicious Javascript on their sites, and the next thing you know, their site cannot be accessed in Chrome, and usually Firefox as well. Depending on what services pick-up on the bad javascript.
For me, it usually takes a day(ish) from the time we are notified of the issue, update the sites, remove the malware, install webmaster tools from Google, submit and wait for the review to be unblocked.
On one hand, this is very frustrating, but on the other hand, many small businesses would have no idea their site had been hacked without it being blocked.
The only thing I'd like to see personally is if Google were somehow able to notify the domain registrant of the block via email so they find out right away, and not after a few weeks (or longer) in some cases. Some small business owners don't check their sites very often. We like to monitor our client sites, but sometimes new clients come to us with these problems and have no idea how long they've been down.
Re: Chrome is blocking wired.com
#57I 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…
https://www.google.com/intl/en/chrome/browser/privacy/
If you don't trust what they are saying there, you shouldn't be using Chrome at all.
Re: Chrome is blocking wired.com
#58Earlier quoted context omitted.
Just accessed it under Chromium Version 33.0.1750.152 (256984) (arch linux) with no problems (except for some lag).
Super weird -- I'm on Arch Linux, too. Could it be DNS-related?
Re: Chrome is blocking wired.com
#59This happens to many small business sites. If they leave their WordPress un-patched, or have a crappy plugin installed with security holes, or their FTP info is guessed, etc, hackers drop some malicious Javascript on their sites, and the next thing you know, their site cannot be accessed in Chrome, and usually Firefox as well. Depending on what services pick-up on the bad javascript. For me, it usually takes a day(is…
I get notified via email when Google finds any issues on my site.
Re: Chrome is blocking wired.com
#60Earlier quoted context omitted.
Just accessed it under Chromium Version 33.0.1750.152 (256984) (arch linux) with no problems (except for some lag).
Super weird -- I'm on Arch Linux, too. Could it be DNS-related?
ps: Mozilla Firefox 31.0a1 is ok with wired.com