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 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 these limits are designed to avoid DoS conditions, but the many > requests we've received, the false positive reports, the threads on this > very ML, clearly showed that the actual implementation isn't > particularly smart. > > Now, the new design goals I have in mind are basically: "keep safe, but > do not annoy!" > In other words, I'd like to keep the internal, configurable limits > nearly as they are (be safe from DoS), but I'd like to get rid of those > "features" that proved to be not useful and very annoying. > > So now the real questions are: > 1- Do you have a real usage scenario for "Oversized.Zip" and friends? > 2- Are you aware of what the ArchiveBlockMax option does and if so, have > you set it to "on"? And why? > > Thanks a lot for your attention and your time. > > -aCaB > > _______________________________________________ > Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net > http://lurker.clamav.net/list/clamav-users.html _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
