[clamav-users] Why is ArchiveBlockMax obsoleted?
dennispe at inetnw.com
Thu Feb 26 13:21:40 EST 2015
Features that have graduated from deprecated to deleted should have all remnants
removed from associated files. Sounds like it's past time to tidy up the
clamd.conf and freshclam.conf files.
On 2/26/15 10:10 AM, Steven Morgan wrote:
> Hi Vladislav,
> Unfortunately there is currently not an option to flag files when
> MaxRecursion is exceeded. Looking at the README, ArchiveBlockMax was
> removed from ClamAV in 0.93, don't know what were the reasons, it was
> before my time. Maybe a search of the mail list archive could give insight,
> or maybe someone else will have some thoughts? You can also open a feature
> request at bugzilla.clamav.net.
> On Thu, Feb 26, 2015 at 4:46 AM, Vladislav Kurz <vladislav.kurz at webstep.net>
>> Hi all,
>> in response to recent wave of viruses that were not detected by any
>> we decided to simply block any nested zip files. (Exe inside Zip inside
>> So I tried to set MaxRecursion=1, just to find out that it passes such
>> as clean without scanning deeper. I want to block such files in the same
>> manner as encrypted archives, but the ArchiveBlockMax option is obsolete.
>> Is there any undocumented replacement option for that?
>> On some man pages I found --max-block, but that is ignored as well.
>> Is there any reason to drop such function?
>> Best Regards
>> Vladislav Kurz
>> Help us build a comprehensive ClamAV guide:
> Help us build a comprehensive ClamAV guide:
More information about the clamav-users