Why would two FF 3.6.6 dll files be flagged as not trustworthy by File Insight feature of Norton Internet Security 2010?
I upgraded from Firefox 3.6.4 to 3.6.6. Before I had a chance to manually run 3.6.6, Norton Internet Security 2010 (v17.7.0.12) Insight Protection feature flagged freebl3.dll and nssdbm3.dll as not trustworthy and put them in quarantine. A manual virus scan of the Firefox folder discovered zero problems.
Norton prompted for a restart to fully "fix" the alleged problem. I uninstalled 3.6.6 (leaving personal data/settings intact), restarted, reinstalled 3.6.6, and manually invoked a Norton File Insight scan of the two dll files. Same results as immediately after the first install of 3.6.6.
I uninstalled 3.6.6, restarted, and installed 3.6.4. A manual virus scan of the Firefox 3.6.4 folder discovered zero problems. A manual Insight Protection scan of the 3.6.4 variant of the freebl3.dll and nssdbm3.dll files resulted in a trustwothy status for both.
The "problem" might, I guess, automatically fix itself, once 3.6.6 is installed by a larger number of people who use Norton Internet Security and have the Community Watch feature turned on.
Later, when I have time, maybe I'll reinstall 3.6.6 and manually "tell" Insight Protection that I trust the two "not trustworthy" dll files. I have no idea if the Community Watch feature will report that decision to Norton HQ.
No big deal, as I'm the least likely person to need the additional 30 seconds of plug-in timeout in 3.6.6.
== I installed Firefox 3.6.6
Todas las respuestas (2)
You can look at the source code if you want: https://developer.mozilla.org/en/download_mozilla_source_code
That's pretty transparent, I think.
From Symantec:
"The issues with Firefox 3.6.6 should now be resolved. You do NOT need to run LiveUpdate to get the fix - this was a back-end change that you should see reflected automatically in the next few hours. Thanks to everyone for alerting us to the problem and for being patient as we worked to fix it. There were some technical irregularities with this Firefox release that caused Norton to make the detection, and we are following up with Mozilla to ensure this doesn't happen again."