• Web of Trust. Godfuckingdammit.
    6 replies, posted
So, I was cruisin' the old intertubes a couple days ago, when I decided to download a song. Googled it, found something on a place called MP3Locker, WOT said it was just fine. Clicked on it, and Avast went fucking crazy. Whole assload of threats detected. Backed out of the website, and a couple minutes later, FF starts opening a bajillion tabs. Closed FF. A few seconds later, BSOD. Computer still isn't working. What the hell. Anybody else ever had WOT fail on them like this?
WOT doesn't generally work. sometimes it will do this shit: [img]http://gyazo.com/d9079aa5d0d4678a5c8c2059d2be91b8.png[/img]
WoT relies on collected information from third parties and users to supply the proper ratings. If that site was new/had a bunch of idiots rating it(or the owners rigging the system) then it's understandable that the ratings were off. Most of the time it's a dependable tool though. However it could pull a SiteAdvisor and start doing tons of misleading unethical crap just for money, which is likely.
Avast has a lot of problems like this. Today it blocked a guy out of facebook and I think google as well.
[QUOTE=McNab;29116924]Avast has a lot of problems like this. Today it blocked a guy out of facebook and I think google as well.[/QUOTE] Oh hell, I didn't even recall that. You're right. OP: avast has been on a rampage of false detections today. You sound like you got an actual infection but there are multiple threads involving this matter. [url]http://www.facepunch.com/threads/1077833-Viruses-on-various-websites[/url] [url]http://www.facepunch.com/threads/1077840-Facebook-is-a-trojan-horse[/url]
There's been a few times where I've had red rated sites to be blocked, but WOT didn't block them. Special circumstances I guess.
OP, sounds like a disaster. There should be a fix for the tab exploitation though. I had to use IE once because of school and a bad link caused IE to open a billion tabs. There was no way to access task manager or do anything. The webpage was stuck. The only way I could fix it was to switch the power off. I'd think that such a loophole would not exist in FF though. I'll be on the lookout for that.
Sorry, you need to Log In to post a reply to this thread.