[clamav-win32] Re: w32.clamav.net

[Nigel Horne]

>   1) Can you describe the tool-chain you are working with on windows?
Visual Studio 2005

> What external packages/libraries have been configured and how were they
> built, where are they stored, etc?

pthread-win32

>   2) It seems that the binary files in the current clamAV.msi were built
> without "SUPPORT FOR DIGITAL SIGNATURES", since freshclam reports this.
> What are the issues and plans in this area?  Can I help?

I am yet to add GMP to the project. It is on my TODO list. You can help
by pointing me in the direction of the correct source version to use, I
hear that some are better than others ;-)

>   3) Are the files generated in when building clamAV.msi, merely built
> from the latest files from cvs.clamav.net? 

Yes, but you need the patches in contrib since not all developers have
included fixes in their code. You'll also need .vcproj files which I can
send you - I haven't bothered to commit them to CVS.


> If not, where can we get the
> actual source files?  It seems that there might be a relationship to
> contrib/Windows/Projects/ClamAV/patches.  Is this patch being kept up to
> date?  Why have some, but not all of the O_BINARY patches been
> incorporated in the mainline code? 

That depends on the author maintaining the relevant code. Some have
agreed to include the patches in their main code, some haven't.


< In any case, some folks have already
> reported issues with the mmap() implementation by reporting error
> messages which match the ones implemented in the
> contrib/Windows/Projects/ClamAV/libclamav/compat.c code.  The attached
> patch fixes mmap() to support multiple concurrent mmap() calls, and
> provides fixes which will work for both the mmap and readdir code when
> compiled for a 64bit OS environment if that ever happens.

Thanks, I'll look into these ASAP.

>   4) freshclam running at the start of the ClamAV service is nice, but
> I'd really hope that the system running ClamAV wouldn't reboot or
> restart the ClamaAV service very often.  Meanwhile, there have been
> virusdb updates for the last few days which have ranged from a minimum
> of 4 up to 8 times per day, so clearly continuously running freshclam is
> desirable.  What are your plans regarding getting both clamd and
> freshclam running in the background?  Can I help?

You *should* be able to call freshclam from time to time with the
Windows XP scheduler, however it is true that I need to get the daemon
mode working, or modify the Windows service program to call freshclam
from time to time.