General Category > General Discussion
Virus?
virtuali:
--- Quote from: HiFlyer on September 07, 2009, 10:40:42 am ---The problem is that users of FSdreamteam products who also have anti virus, are being intermittently inconvenienced by these episodes
--- End quote ---
The issue is, you are seeing it backward: the problematic software is not FSDT, it's the antivirus that, after a certain update, has decided that a software (the SAME software) that was ok up to last week, has now suddendly become a virus, without this being changed at all.
So, it's clearly the antivirus fault. The job of an antivirus should be protecting from a virus WITHOUT interfering with the software, and the onus of trying to be reliable at this, it's on the antivirus developers.
--- Quote ---Isn't there any way for Coautl to do whatever its doing in such a fashion as to not cause so many false positives?
--- End quote ---
Think about it: if it was possible to conceal from the antivirus from our side, real virus could it just the same. This is what real viruses usually do as well, which is what the antivirus tries to prevent.
The more real viruses become smarter avoiding to be detected (in a sense, you are suggestiong we should become smarter at that too...), the more the antivirus has to use wild guesses of what could be a threat, and the more false positive you'll get.
That's why it's important being able to manually exclude files from scanning, since the whole process is *inherently* unreliable.
--- Quote ---Surely there are other products that are "protecting" themselves in ways that do not cause these issues?
--- End quote ---
No, see this post at Flight1 forum:
http://www.simforums.com/forums/forum_posts.asp?TID=24061
They have exactly the same problem with their wrapper, and the solution proposed is exactly the same as ours: manually exclude the affected files from scanning or, if the antivirus doesn't allow it (like McAfee Home edition), switch to a different product.
dsktopflyr:
I have appealed to McAfee's reply to this file being identified as a virus. The type of virus couatl.exe is being associated with w32/induc!a has something to do with files programed with Delphi (http://vil.nai.com/vil/content/v_204731.htm). Again, I believe this to be a McAfee problem and before I consider to get rid of McAfee I am using all channels available to get the problem resolved.
virtuali:
You can try to update to the latest version (just run any scenery installer again), we have done some changes, that will hopefully improve compatibility with McAfee now.
dsktopflyr:
Thanks Umberto I will give it a try. Just a heads up my appeal to McAfee appears to be working it's way through the process. They returned my email this morning at 2:36AM EST. The file couatl.exe is now identified as inconlusive. Hopefully the will come to their senses and update the DAT file now in the next few days.
Avert(tm) Sample Analysis
Issue Number: 5492852
Virus Research Analyst: Neha Chattopadhyay
Identified: Inconclusive
McAfee Avert(tm) Labs, Bangalore, India
Thank you for submitting your suspicious file.
Synopsis
http://vil.nai.com/vil/content/v_204731.htm
We currently have, in our latest engine and DAT files, detection for over 120,000 viruses and trojans. Though we are now making a concerted effort to get a description of every virus in the wild in our Virus Information Library, we have not yet reached that point. We appreciate your patience and your request for this information.
HiFlyer:
--- Quote from: virtuali on September 08, 2009, 11:21:18 am ---You can try to update to the latest version (just run any scenery installer again), we have done some changes, that will hopefully improve compatibility with McAfee now.
--- End quote ---
(Heaves Huge sigh of relief)
Thank you! This was driving me crazy. I hope it works for a good long while!
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version