On 09/01/2012 11:56 PM, Ant wrote: > The problem is that those files are very new and unknown. So Norton is > supsicious of them. Also, using beta/prereleases doesn't help since they > can change again soon. It is good to submit those suspicious files, but > note that it will happen again.
Ummm, no: <https://duckduckgo.com/?q=freebl3.dll+%2B+norton> <https://encrypted.google.com/#hl=en&output=search&sclient=psy-ab&q=freebl3.dll+%2B+norton&oq=freebl3.dll+%2B+norton&gs_l=hp.3..0i30.7820.11275.0.11578.10.10.0.0.0.0.160.1262.0j10.10.0.les%3B..0.0...1c.Zki4-csTlFA&pbx=1&bav=on.2,or.r_gc.r_pw.r_qf.&fp=4c5ca94259600d8c&biw=1280&bih=733> <https://duckduckgo.com/?q=nssckbi.dll+%2B+norton+%2B+norton> <https://encrypted.google.com/search?hl=en&q=nsschbi.dll%20%2B%20norton#hl=en&sclient=psy-ab&q=nssckbi.dll+%2B+norton&oq=nssckbi.dll+%2B+norton&gs_l=serp.12...0.0.0.73302.0.0.0.0.0.0.0.0..0.0.les%3B..0.0...1c.Ihox-XNiAdk&pbx=1&bav=on.2,or.r_gc.r_pw.r_qf.&fp=4c5ca94259600d8c&biw=1280&bih=733> Note: I wonder why it is so difficult for you to bottom post... > > > On 9/1/2012 9:08 PM PT, Justin Wood (Callek) typed: > >> Hey Guys, >> >> Just wanted to followup on status here >> >> So there has been a related thread about SeaMonkey 2.12 issues and >> Norton Antivirus. It has been reported that that specific [SeaMonkey >> 2.12] problem is fixed. >> >> However, I wanted to let you know that JUST NOW, when I let my Beta >> version of SeaMonkey 2.13 update I got the same Norton issue ("based on >> a heuristic scan" it says) for two of my SeaMonkey DLL's nsschbi.dll and >> freebl3.dll. >> >> It popped up a small warning in my taskbar and I had to open the Norton >> UI, go to "History" open up "Options" and I selected "restore and >> exclude" to get it back to working. >> >> I am still awaiting a human response to my Norton e-mail, and will >> likely look up a corp phone number on Wednesday if I haven't heard back >> by EOD tuesday to see how we can address this on their end going forward. @Justin: Send them the links that I've provided & remind them that this is not the first time their (cough) "anti-virus" has done this. Sample from 2010: <http://www.h-online.com/security/news/item/Norton-produces-false-alarm-after-Firefox-update-1030099.html> FYI, one of the first things that I started doing years ago on my client Window machines is purge anything Symantec/Norton. None of those clients have ever been infected by a virus. @Interges (who's posts I didn't/won't see because I have all things Google Groups filtered to dev/null): see above. I recommend that in the future you look to your "anti-virus" vendor for explanations as to why they still can't get this right despite several years of false positives. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
