aCaB wrote:
> Hi list.
> I'm in the process of redesigning the logic of limits in ClamAV.
> The rewrite (scheduled for the upcoming 0.93) is aimed at solving, once
> for all, the annoyances related to config options like
> (clamd.conf-style): ArchiveMaxFileSize, ArchiveMaxRecursion,
> ArchiveMaxFil
The oversized zip setting can get very annoying, especially if you are
using KlamAV or some other GUI. To the second, I do not use it, though I
do know what it is.
On Tue, 2008-01-29 at 17:30 +0100, aCaB wrote:
> Hi list.
> I'm in the process of redesigning the logic of limits in ClamAV.
> The rew
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi aCaB:
Since you've clarified your meaning, I can state that I don't use
those features.
On Jan 29, 2008, at 12:07 PM, aCaB wrote:
> James Kosin wrote:
>> Maybe, put a warning in the email message clarifying that the file
>> could
>> not be ch
James Kosin wrote:
> Maybe, put a warning in the email message clarifying that the file could
> not be checked by clamav instead of flagging as an 'Oversized.Zip'
> virus. This may be more useful for the receiver and sender to know than
> to actually cause an annoying DoS prevention.
Hey James
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
aCaB wrote:
| So now the real questions are:
| 1- Do you have a real usage scenario for "Oversized.Zip" and friends?
Maybe, put a warning in the email message clarifying that the file could
not be checked by clamav instead of flagging as an 'Oversize
Hi list.
I'm in the process of redesigning the logic of limits in ClamAV.
The rewrite (scheduled for the upcoming 0.93) is aimed at solving, once
for all, the annoyances related to config options like
(clamd.conf-style): ArchiveMaxFileSize, ArchiveMaxRecursion,
ArchiveMaxFiles and so on...
All the
