Many of you have noticed that the NOD32 virus scanner by ESET has been incorrectly identifying minirosetta as a variant of a "Win32/Statik" virus.

This is an issue very difficult to resolve for us: We have no contorl over ESET's virus definition files, nor do we know what it is that NOD32 supposedly recognises. We also have little control over the binary code Visual C++ produces from our code. We have contacted ESET about this but they have been rather unhelpful.

For now thus, all i can offer is a workaround: If you turn off Web access protection for *bakerlab.org* addresses, this should avoid the problem.

Go to setup->"Antivirus and antispyware"->Configure...

and then under
Antivirus and antispyware-->Web access protection->Excluded addresses

click "add" and type in *bakerlab.org*
(asterisks are required on both sides!)

and then OK.


I've tried this on my local virtual windows machine and it appears to work. Please let me know if it does for you too ! We'll try and resolve the issue "properly" but it will be some time before we'll be able to, for now i hope this workaround is acceptable !

Cheers, Mike

---

http://beautifulproteins.blogspot.com/
http://www.miketyka.com/

i would suggest that people with the problem contact NOD's authors (ESET) and post in their forum or use the 'contact support' link to give them some idea of how large the user base (and therefore the problem) here is. The longer it carries on, the more members the project will loose...

http://www.eset.com/support/kb.php

---

Thanks much for the workaround. It will take me some time to deploy that globally -- but that sounds like a fix.

Barry

Many of you have noticed that the NOD32 virus scanner by ESET has been incorrectly identifying minirosetta as a variant of a "Win32/Statik" virus.

This is an issue very difficult to resolve for us: We have no contorl over ESET's virus definition files, nor do we know what it is that NOD32 supposedly recognises. We also have little control over the binary code Visual C++ produces from our code. We have contacted ESET about this but they have been rather unhelpful.

For now thus, all i can offer is a workaround: If you turn off Web access protection for *bakerlab.org* addresses, this should avoid the problem.

Go to setup->"Antivirus and antispyware"->Configure...

and then under
Antivirus and antispyware-->Web access protection->Excluded addresses

click "add" and type in *bakerlab.org*
(asterisks are required on both sides!)

and then OK.


I've tried this on my local virtual windows machine and it appears to work. Please let me know if it does for you too ! We'll try and resolve the issue "properly" but it will be some time before we'll be able to, for now i hope this workaround is acceptable !

Cheers, Mike

---

*bakerlab.org* is not good as an URL mask. Consider:

http://www.malware.com/bakerlab.org/malware.js

It would be excluded from protection. A security risk.

As a rule of thumb, URL addresses must not contain leading asterisks. Change it to:

srv?.bakerlab.org*

Cheers.

Or consider a different A/V vendor, perhaps AVG. It's available in a free edition too,..

*bakerlab.org* is not good as an URL mask. Consider:

http://www.malware.com/bakerlab.org/malware.js

It would be excluded from protection. A security risk.

As a rule of thumb, URL addresses must not contain leading asterisks. Change it to:

srv?.bakerlab.org*

Cheers.

---