DO NOT COPY AND PASTE THE ERROR SCREEN WITH LINKS BACK HERE.
The next culprit will get bin time.
It probably doesn't help when people post the links, lol.
I haven't had a warning today yet.
Sandboxes can be broken. And are. They help, they don't prevent. Actually Chrome is working on a sandbox breach right now.
It really worries me how many people seemed to continue onto the site while Jason was still fixing it. Google does not black list lightly. There is usually a very good reason. It is all too easy, not because of the SA's being lax, but because of the sophistication of the attack software available. We are long past the days of simple "I LOVE YOU" and "Nigerian money transfers." Unfortunately, a few real jerks are ruining the internet for all of us. The penalty is Google and others have to spend a LOT of money ( and we all pay for it somehow) to protect us the best they can. Don't get mad at them because we were interrupted a few hours, get mad at the hackers. They messed up Jason's day too.
I run ghostery all the time, so, google can blacklist the site all it wants for some ad or link, but I'll never see it...and if you do, you aren't being proactive enough.
Anyone browsing the internet without ghostery or noscript nowadays should really have their head examined.
Always make sure you have your internet prophylactic on.
Thanks for the images - yes this is what I was after, in order to avoid the links going into the thread itself.
Great, well, the good news is that all the stuff mentioned on that screenshot was dealt with long ago and is done and dusted.
The bad news is for some reason you're still getting a warning about that same, now fixed, problem. I'm not sure what can be done about that - as far as I can conclude at this stage, I'm guessing either your browser has some setting that will continue to throw this warning for the next 90 days (the info page itself says the site is not listed as suspicious, but was flagged in the last 90 days), or your browser is accessing an old/cached malware database. I'm not sure there is anything I can do about that.
Possibly. I'm really not sure. It could be your ISP caching something (even a hard refresh may not give you the ability to refresh something stuck in your ISPs cache). You could try switching to a different ISP (for example, tether / hotspot your phone to your computer if your regular internet company is different from your phone company), doing a hard refresh once you are using the new ISP, and see if you still get the warning.
Everything has been done now for diyaudio.com - it's clean with Google, and it's clean with StopBadWare, which is the totality of advice from Mozilla (Firefox Phishing and Malware Protection).
Try pressing <ctrl> F5 This *should* cause upstream proxies to refresh their cache even if they don't think that they need to, at least I think it used to work that way. Worth a try.
Tony.
Tony.
Mine seems ok now, thanks to the admin team...
I think there is someones fingerprint on this Firefox block. The more I visit this site the emptier my wallet is. Probably "Diyaudio Wives" organized this thing to spend more time with husbands.
I think there is someones fingerprint on this Firefox block. The more I visit this site the emptier my wallet is. Probably "Diyaudio Wives" organized this thing to spend more time with husbands.
Not since then no. Can't duplicate what I did as I think it was the result of a google search, and I can't remember what I was looking for. 😀
Cleaned cache, deleted history - impossible to get in without the warning!
No problems with any other site.
This at 10.38 GMT.
Firefox 17.0.1
Mac OS 10.7.5
No problems with any other site.
This at 10.38 GMT.
Firefox 17.0.1
Mac OS 10.7.5
Hi,
Just tested diyA on 4 different computers.
XP IE8 and FF17.01 > Ok
Win7 IE9 and FF17.01 > Ok
Win8 IE10 > Ok
Ubuntu 12.04 FF17.01 > Ok
I have no issues (yet) since Jason declared OK.
Just tested diyA on 4 different computers.
XP IE8 and FF17.01 > Ok
Win7 IE9 and FF17.01 > Ok
Win8 IE10 > Ok
Ubuntu 12.04 FF17.01 > Ok
I have no issues (yet) since Jason declared OK.
The Google Safe Browsing which was the trigger for the FF and Chrome alert,
has no issue with this site since 24 December:
Google Safe Browsing diagnostic page for www.diyaudio.com
--
SB
has no issue with this site since 24 December:
Google Safe Browsing diagnostic page for www.diyaudio.com
--
SB
If you receive a warning please do a screen capture of the alert information and post it here if at all possible. The site has been clean for days, this seems to be a Google issue.
Strangely enough I have FF 17.0.1 at home and at work, and at home in both Linux and Win 7 flavors. I have not received an alert at work, but have received them at home on browsers in both OS as recently as two days ago - will have to check as I have not been online at home since Wednesday.
Strangely enough I have FF 17.0.1 at home and at work, and at home in both Linux and Win 7 flavors. I have not received an alert at work, but have received them at home on browsers in both OS as recently as two days ago - will have to check as I have not been online at home since Wednesday.
You may get it on others, but to be useful you need to read the actual google page with the reported links and take a snap shot of that. The red screen of death (as I call it) is generated by Firefox.. Click on the button I've illustrated in my attachment next time it occurs, copy the resulting screen and post here. And thanks!
Attachments
I just got one too. was clear all yesterday. Only the one so far. and as has been the case almost every time it is when clicking on a link from within the user control panel to look at a subscribed thread. Looks like the same message as before.
Firefox 17.0.1 Windows XP SP3.
Tony.
Firefox 17.0.1 Windows XP SP3.
Tony.
Attachments
- Status
- Not open for further replies.