Paul B. Gallagher <[email protected]> wrote: > Yesterday, I wrote: > >> Rob wrote: >> >>> As a customer of Norton you should be able to file a false positive >>> report and hopefully get it resolved. >> >> I did, here: >> <https://submit.symantec.com/false_positive/> >> >> I did have to specify which program and version was alerting. >> >> They promised a response within 48 hours. > > Sure enough, they just wrote back (after 12 hours) to say they'd cleared > the file and would remove its detection from their products. Then they said: > > "This message (including any attachments) is intended only for the use > of the individual or entity to which it is addressed ... any use, > dissemination, distribution, or copying of this communication is > strictly prohibited." > > <whisper>So don't tell anyone you heard this from me.</whisper> > > They also offered a link for software developers to submit their > products for whitelisting, but I'm not sure if I'm allowed to disclose > that confidential information. ;-)
The Mozilla developers have tried to do that many times and it has not worked. That is why you had the problem. Apparently the Norton people have put a too broad virus definition in their database and it triggers with every Mozilla release. When you report a false positive they don't sit back and think "what causes this and how can we modify the signature" but they just put in a whitelisting entry that exactly matches (the signature of) the file you submit. Next time a new Mozilla release ships, the file is slightly different but still matches the broad virus pattern, and the same will happen. Ad infinitum. The only way you can get rid of this is by switching to a better anti-virus product. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
