I am having a problem with rosetta functioning properly with my anti-virus software, Kaspersky. Kaspersky I.S. contains an application firewall that assigns certain privileges to programs based on whether or not it thinks they are potentially dangerous. It is consistently categorizing minirosetta as "untrusted" and block it from all network use. I can manually unblock it, but every day kaspersky re-categorizes it (I think because BOINC re-downloads it with a new work unit). Is this even a problem? The BOINC client has full network access. Why does kaspersky hate mini rosetta?

-James

I'm also STILL having this problem (almost a year on from the OP) with the latest version of KIS2009.

All the other BOINC runtimes play nice with Kaspersky, so what aspect of minirosetta's activity is triggering the heuristic blocking in KIS?

---

I've been struggling with this very same issue for some time now as well. Kaspersky IS2009 (KIS) has no trouble with ANY other BOINC projects, but every new version of MiniRosetta (MR) sets off KIS alarms. MR 1.75 & 1.76 both cause the following KIS warning to be repeated about once every second when MR tries to start:

[date][time] minirosetta_1.75_windows_intelx86.exe Autorun Denied: KLPrivileges/KLSelfStart

I don't completely understand the meaning of this message, but I do know that KIS's "Proactive Defense" will ignore any app if it is either digitally signed or if the app is already listed as 'safe' in the KIS database. MR does not satisfy either of these requirements. I do not understand why Baker Lab can't digitally sign MR.

I have put up with this problem long enough though. If the next release of MR is not digitally signed and KIS refuses to run it, then I will be removing MR from the 6 PC's I am running it on. I do not have the time to manually transfer this app from the 'Untrusted' to the 'Low Restricted' group every time a new release appears.

---

Yes. I have submitted a false positive fix request to Kaspersky, but Rosetta@home really needs to digitally sign their software. No other BOINC project has this problem.