On Wed, 03 Dec 2003 11:49:11 +1300 Jason Haar <[EMAIL PROTECTED]> wrote:
> On Wed, 2003-12-03 at 09:38, Matthew Trent wrote:
> > Ok, when the ArchiveMaxFileSize is set higher, the file goes
> > through. I also see the new ArchiveMaxCompressionRatio option; I
> > assume that's intended to safely allow a larger ArchiveMaxFileSize?
> > What about an option to return success and a log warning instead of
> > an error when the size limit is reached?
>
> Indeed - the commercial AV products do that. If you set a max level of
> checking, they simply stop processing after their internal limits have
> been reached.
I think clamd should continue archive scanning and just skip files
bigger than ArchiveMaxFileSize (and of course log them). Also we can
make recursion and file number limits not critical and only log files
that break them. However there is a small problem with clamscan because
in contrast to clamd most users don't use the logger (-l). That's why I
think something like --ignore-limit-errors should be implemented (and
may be very useful in mail scanning software). I will fix it tomorrow.
Thanks for the discussion.
Best regards,
Tomasz Kojm
--
oo ..... [EMAIL PROTECTED] www.ClamAV.net
(\/)\......... http://www.clamav.net/gpg/tkojm.gpg
\..........._ 0DCA5A08407D5288279DB43454822DC8985A444B
//\ /\ Wed Dec 3 00:14:57 CET 2003
pgp00000.pgp
Description: PGP signature
