On Mon, 3 Nov 2003 13:35:50 -0500 (EST) Ed Phillips <[EMAIL PROTECTED]> wrote:
> clamscan detects the "broken on purpose" ZIP files and reports an
> error message (correctly), when you scan the ZIP file directly or when
> you scan the directory containing the broken ZIP file. clamd, however,
> ignores all errors while scanning a directory hierarchy, so in the
> case where it's scanning a directory that contains only the broken ZIP
> file, you get an OK message from clamd (very broken behavior IMO!).
This is already fixed in CVS:
Sun Oct 26 06:26:14 CET 2003 (tk)
---------------------------------
* clamd: report file errors with CONTSCAN (suggested by Daniel Fraga)
> Yes, I know 20030317 is very old, but it has stayed running since the
> time we installed it, and the more current snapshots of clamd crash
> pretty quickly for us. And, it appears clamd still works the same way
20030317 contains _two_ dangerous race conditions and I don't believe
it's stable.
Best regards,
Tomasz Kojm
--
oo ..... http://www.clamav.net/gpg/tkojm.gpg
(\/)\......... 0DCA5A08407D5288279DB43454822DC8985A444B
\..........._ Tue Nov 4 00:38:46 CET 2003
//\ /\
pgp00000.pgp
Description: PGP signature
