Ryan wrote:
Nigel,
Since I couldn't find any other reference to current CHM bugs at clamav.net
I went ahead and posted one:
https://wwws.clamav.net/bugzilla/show_bug.cgi?id=742
Thanks. 740 and 742 now cover it, so it's "in the system".
They seem pretty emphatic about not supporting clamav-win32...
"Please do not report any bug affecting software derived from ClamAV and
distributed by a third party (e.g. ClamWin, clamav-win32, ClamXav) because
we have no control over them. Contact their developers instead. Bugs in the
CygWin based ports like ClamWin and clamav-win32 should be reported to Reini
Urban"
ClamWin, clamav-win32 and ClamXav are indeed 3rd party products, so we can't
help. It's
rather confusing because what you're probably using is the "official" binary
build
for Windows of ClamAV from w32.clamav.net, which people also call clamav-win32.
Anyway, what you've done is spot on, and thanks for raising it, it is now in the
system.
To avoid any further doubt though, I get the same results when scanning the file
under Linux, it is therefore a clamAV generic issue (which has also recently
been
discussed in clamav-users).
Ryan
-Nigel
_______________________________________________
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-win32
