All should now be ok. We’ve had an update Kevin Haley at Symantec today (12/7/14) as below so all issues with False Positives should now be resolved.
[quote]It looks like I need to eat some humble pie. We did not fix this issue. My apologies for this. And for misleading you.
As you know we white listed the first set of files, so those will not experience an FP. Last night, based on your email/submission to us, the team white listed the new files. So there will not be problems with the current group of in-field files.
What we wanted to solve was the issue with new files that you create. We thought we had that in place. Obviously it was not. We had some QA issues that made it harder for us to spot the problem. Today we re-grouped. We are looking into root causes. However, while that is ongoing we have taken two additional steps, a belts and suspenders approach, to avoid further issues with new files you release.
In short, given the digital signatures used with your files and the reputation of the URLs used to download your files, we should not have had a false positive on any of your files. While we look to find the problem, we have instituted two additional safeguards, which will prevent false positives, even if the root cause of the original false positive is not discover.
While I realize that my creditability is certainly to be questioned on this subject, I do believe that we have put the safeguards in place to prevent future problems.