Re: A MAJOR problem with "remote" scanning using ClamAV

I was wrong when I said "I *never* noticed that option in clamd.conf, nor had it occurred to me that there might be such"!

I looked back at my years-old (2014) clamd.conf file and found that I had, at the time (version 0.99) started using the StreamMaxLength and a couple of other options when I set up clamd for purely local use. And over those 11 years, I just copied the file forward without really thinking about it, as it always "just worked".

Then, when I started using clamdscan over TCP rather than locally with "--fdpass", the limit was only now applied -- at 100MB (since I started with the default clamd.conf, rather than copying my own version).

So I can fully understand how bugs can be hiding for years and years.

Paul


On Tue, 2 Dec 2025 12:56:35 -0500
Paul Kosinski via clamav-users <[email protected]> wrote:

...
> I never noticed that option in clamd.conf, nor had it occurred to me that there might be such.  
_______________________________________________

Manage your clamav-users mailing list subscription / unsubscribe:
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/Cisco-Talos/clamav-documentation

https://docs.clamav.net/#mailing-lists-and-chat