When was Safari's "Warn when visiting a fraudulent site" switch added to the Prefs? 3.2.1 ?

A friend ran into the effects of this last night. She published her website via iWeb about 2 years ago to a host.
She did one minor text update a year ago.

Last night, she went to her site, and was greeted with an alert:

<<inline: Picture 3.jpg>>




If you follow through with this, you end up having to LOG INTO Google via a google account ... and use their webmaster tools in order to solve the problem.

I called her hosting service and they said that the solution is to

a) republish the site
b) submit the site to Google for approval so the site can be taken off the blacklist

I was nonplussed by this concept.

The site comes up with Firefox, but not with Safari.
At which point, I wondered if Safari was consulting a Google database every time you clicked on a site?

I opened Safari prefs and found the switch for fraudulent sites under Safari's security settings.
I'd never noticed it before.

After turning the switch off, the site loads fine.

What likely happened is that a site that was being hosted under that shared IP on her service providers server was the site containing malware. The report I read regarding her site suggests there were trojans and other javascript exploits coming from her site. Of course, if they were, they were tied to the IP of the server, not her site. Nonetheless, the service provider says that even if she moves her site to a different host, her domain name is still probably blacklisted. Unbelievable!

Further, I'm wondering if Safari is checking a Google database for every site you hit if that switch is turned on. And if that's the case, is Google essentially collecting data on every website you hit?

Does anybody know much about what's going on behind the scenes with Safari's "Fraudulent sites: " switch?

K



_______________________________________________
OSX-Nutters mailing list | [email protected]
http://lists.tit-wank.com/mailman/listinfo/osx-nutters
List hosted at http://cat5.org/

Reply via email to