I've been having major issues with NIS 2010 detecting critical components of Firefox (the dlls that control internet usage, plugin-container.exe, etc.) as "threats" based solely on, if I'm reading the information about this "WS.Reputation.1" right, the fact that not many people have used it and it was released recently. Considering there are those of us in the community that are testing nightly builds with constantly changing files, is there a way to disable checking for WS.Reputation.1?
My Firefox install has been corrupted twice because of this "threat removal." I've normally been quite satisfied with Norton, but if it continues to make software unusable, I don't know if I can continue using it. I should also add that this first started being a major issue for me on May 6, right after I'd done a nightly build update. It has since started to affect beta versions as well.
I've been having major issues with NIS 2010 detecting critical components of Firefox (the dlls that control internet usage, plugin-container.exe, etc.) as "threats" based solely on, if I'm reading the information about this "WS.Reputation.1" right, the fact that not many people have used it and it was released recently. Considering there are those of us in the community that are testing nightly builds with constantly changing files, is there a way to disable checking for WS.Reputation.1?
My Firefox install has been corrupted twice because of this "threat removal." I've normally been quite satisfied with Norton, but if it continues to make software unusable, I don't know if I can continue using it. I should also add that this first started being a major issue for me on May 6, right after I'd done a nightly build update. It has since started to affect beta versions as well.
Hi GregW17,
Welcome to the community!
As far as I could see, this problem impacts those users who have the download intelligence turned on or right click and run the Insight Network Scan. So, turn off the download intelligence and it should keep you away from the WS.Reputation.1 alerts. I'm sure the Norton employees are working on gathering information. I won't be surprised if you see anyone bump on this thread sooner and ask you for more information.
While they work on a fix, this might be considered a workaround. Let us know how you get on.
No help... even after disabling download intelligence. I think it's the insight protection that's doing it... Any way to disable the insight protection for just Firefox without excluding it from scans outright?
I've been having major issues with NIS 2010 detecting critical components of Firefox (the dlls that control internet usage, plugin-container.exe, etc.) as "threats" based solely on, if I'm reading the information about this "WS.Reputation.1" right, the fact that not many people have used it and it was released recently. Considering there are those of us in the community that are testing nightly builds with constantly changing files, is there a way to disable checking for WS.Reputation.1?
My Firefox install has been corrupted twice because of this "threat removal." I've normally been quite satisfied with Norton, but if it continues to make software unusable, I don't know if I can continue using it. I should also add that this first started being a major issue for me on May 6, right after I'd done a nightly build update. It has since started to affect beta versions as well.
Greg,
Thank you for bringing this issue to our attention. Over the weekend, we contacted the Firefox development team and have identified a solution that we will be putting in place. Just to be clear, we are only seeing this issue on the nightly developer builds of Firefox and users of the official release are unaffected. Until then, abro has identified a workaround for users that need to interact with very new development code. Please see his response in the following thread. Apologies for any inconvenience, it should be fixed shortly.
Thanks jeff. I've been seeing a couple random cases where Norton picks up the same WS.Reputation.1 with the beta version of Firefox as well, although not as much as the nightly ones. Glad you guys found a solution as well for this!