Could be--the file appeared to be obfuscated when I opened it in Notepad. At any rate, Clam recognized it as malware when scanned from the Windows Explorer context menu, but when I activated the .exe in my virtual machine, ClamMon checked and said it was okay. Evidently, the monitor wasn't using the full Clam library like the clamscan was.

I guess we'll just have to wait for version 1.0.

Regards,

No, it injects it's library in each process and intercepts CreateProcess* functions. Only reason I know is the national encondings - I do some reconding and it works for Russian cp1251, but I don't know about other codepages...

GuitarBob: hmm, using full clam library? I can post the source, maybe I do something wrong, for example loading the db?

Well, in the current version 0.93 the DB files have different names now, and there are only two files. The daily DB file is now called daily.cld. The main DB is main.cvd, but I think it will change to main.cld when it is changed to include the daily.

I will not be much help with the source code--I'm not a programmer.

Regards,

Post the source, I'll be happy to check it out and lend a helping hand if you need it.

bubzie11:
This is a virus i downloaded it and avast professional picked it up as a winshock trojin

do not download!!!

I understand the developer has stopped his work on the program.

We are better off waiting for the resident/realtime/on-access version of ClamWin (development continues--no release date).

Regards

url removed

Just an idea I don't meet yet in any commercial AV software: add option not to scan files that current user can't write. What this mean? In my network I have many windows workstations where users have very restrictive permissions, and the places where users could write limited to user profile and some network shares. There is no mutch sense to check every file -- we need only scan those that user have write access. I think, such option will improve performance.

I've removed links to be sure since of some reports in this post, but the files do not look suspicious to me

MNR: With the ClamWin configuration options, you can manually configure Clamwin to exclude certain directories from scans done at each of your workstations, and you can also configure it to scan only for files with extensions that you select.

Regards,

Thanks, I know it. But it's duplication of effort: first administrator set rights on filesystem, and than he must mirror them in such exclusion list.

The point is, this exclusion list could be generated as sheduled job. But in that case it could be per-user.

Hello all,I just wanted to introduce myself,I am new here and I hope to have a very nice time on this forum.

can we get this intagrated in to clamwin