Virus dectection (false) in Firefly 2.95

Started by Gerald Sutherland, June 16, 2009, 11:48:00 AM

Previous topic - Next topic

Gerald Sutherland

Hello,

I just wanted to let you know that the Kaspersky 6 anti-virus software is detecting the Trojan.Win32.Buzus.bezv in Firefly 2.95 and destroys the Firefly.exe as well as the install package.

I am confident that this is a false detection, but I thought people might want to know so that they can take steps to prevent thier installation from being destroyed like mine was.

Jerry

TechSupport

This has now been fixed. Now using a new encryption process and ran it past virustotal.com without any problems.

Gerald Sutherland

Hi Paul,

I've had Firefly 2.95 on my computer for quite some time with no problem (so I assume that Kaspersky had suddenly become a bit hypersensitive and the problem was on their side of the fence).

I just downloaded 2.99 and all seems well, thank you!

Now I just need to get around to requesting the new key code. :-)

Thank again! :-)
Jerry

Brian Chirgwin

Quote from: Gerald Sutherland on June 16, 2009, 11:48:00 AM
Hello,

I just wanted to let you know that the Kaspersky 6 anti-virus software is detecting the Trojan.Win32.Buzus.bezv in Firefly 2.95 and destroys the Firefly.exe as well as the install package.

I am confident that this is a false detection, but I thought people might want to know so that they can take steps to prevent thier installation from being destroyed like mine was.

Jerry

Yes, this happened to me quite recently (last 2 weeks). I had to download a new version from the web site as it deleted every version of the FireFly.exe on my computer including the ones in the zip files.  Reminds me that I need to write a DVD of all my installations.


Gerald Sutherland

Hi Brian,

That's just what happened to me. All was well for a long time, then suddenly Kaspersky decided to kill the Firefly.exe as well as the install file. So I waited a few days to see if any updated virus identification files would clear up the problem, but no luck. I'm on a company network so I was unable to flag the files as "safe" ... I just had to wait and hope.  Anyway, version 2.99 has taken care of the problem. :-)

Again, my thanks to Paul. :-)

Jerry