INNO - {app} is OK

For some time I'm seeing in my in-depth scan logs:

C:\Documents and Settings\...\CryptoSuite\cryptosuite_setup.exe » INNO » {app}\Cryptosuite.exe - is OK
C:\Documents and Settings\...\CryptoSuite\cryptosuite_setup.exe » INNO » {app}\cryptosuite_benchmark.exe - is OK

(I've left out the full path in the copy of those scanlog lines).
The file cryptosuite_setup.exe is the install file for CryptoSuite (version 1.100). Older members here may remember CryptoSuite from Jason/GhostSecurity; we had a forum for it here, now in this archived forum.

I know there's nothing to worry about those scanlog items but I thought it better to let Eset know. I can submit it if Eset want me to do so.

MD5 checksum (as calculated by CryptoSuite):
The file C:\Documents and Settings\...\CryptoSuite\cryptosuite_setup.exe has the following Checksum(s)
MD5 - AC806F0D4831B41E5A6C3A39B3D00F6B

NOD32 4.2.71.2 on XP-home SP3; pre-release updates not enabled.
Virus signature database: 7994 (20130211)
Update module: 1041 (20120430)
Antivirus and antispyware scanner module: 1381 (20130207)
Advanced heuristics module: 1138 (20121210)
Archive support module: 1160 (20130206)
Cleaner module: 1059 (20121212)
Anti-Stealth support module: 1038 (20130110)
ESET SysInspector module: 1231 (20130121)
Self-defense support module: 1018 (20100812)
Real-time file system protection module: 1006 (20110921)

 

What's the problem?

 

Hi Marcos,

Not very much of a problem. Two reasons for posting it:

1.
Making Eset aware of it in case needed.

2.
Maybe more this reason:
I am curious why it suddenly showed up in my in-depth scan (I always use that, and frequently) logs.
The first time was at 26 Jan 2013 (with virus signature database: 7934).

So, I guess the question is: why did it suddenly showed up?

 

Perhaps it's because the Archive module has been updated and added support for additional packers.

 

Yes, I know very well that it could be related to an updated Archive module .
If my memory serves me well: when such things happened in the past, it was "fixed" after awhile by Eset. That was the other reason why I posted it. Search the Eset forum for INNO in the thread title; yes, I know that that were other kind of "warnings".
BTW, this is a very old file. It was first seen at VT almost 5 years ago.

 

Well, it turned out this is not something new and the Inno installer was scanned this way with archive module 1147 (released in June 2012) and newer.

 

OK, thanks Marcos. Why I started to see those particular lines in my scan-logs at about 26 Jan 2013, I don't know. So be it.

Anyways, it isn't of course that important and I have let you guys know now about it (if needed at all).
Time to move on