Quote:
Originally Posted by DiapDealer
I can happen on any mediafire download.
The only evidence I have is that if I restrict scripts (with NoScript) to only those that originate from mediafire (usually flash related), I've never seen an issue.
The problem usually arises from websites that use an ad service that doesn't properly vet their ad sources. Rogue antivirus's and other malware can be contracted from perfectly innocent websites that utilize a suspect ad-service. Anyone on a Windows machine that doesn't use NoScript (or NoAd as others have mentioned) is really taking a risk visiting any website that utilizes an ad service.
|
I appreciate this explanation, and it matches what I've seen. It's not every visit to MediaFire that's given me headaches...only three.
I also use Firefox with NoScript and ABP. And I can't think of any site I've ever visited where I've allowed all scripts. I usually start with the most obvious one (e.g., allow MediaFire on the MediaFire site), and then click up through the various options, if that doesn't allow me to do what I need. I don't remember allowing any other scripts on that particular page, but I suppose it's possible that I approved a script source on a
different page and it crossed over?
I wish there was a way to research what the various choices do before allowing them. As of right now, there are five options for the MobileRead pages alone - and the basic "allow MobileRead" doesn't give full functionality to the site.