On Mon, 6 Oct 2025 10:14:53 -0700 Kenneth Porter via clamav-users <[email protected]> wrote:
> Can a down-level clamdscan client (orphaned by the recent deprecation) > interoperate with a current version clamd server on another host? > > If not, what are the build and runtime requirements for the current client? ----------------------- I've gotten this to work (as far as I can tell) but it's not pretty: Setting up to scan remotely is very unintuitive and weird: you have to make a fake clamd.conf and explicitly set the options "TCPAddr [remote-IP]" and "TCPSocket [remote-port]". However, the description in the sample file talks about "TCPAddr" as an address to *bind* to (instead of INADDR_ANY), which is nonsense for a *remote* IP address. But at least if you ever want also to run a local clamd (for different virus defs or such) you can explicitly tell clamdscan which so-called clamd.conf to use. In detail, my "server" is running ClamAV 1.0.9, while my "client" is 0.103.6, and was not specially built. My client is running on my Postfix machine and is used for scanning email. (It used to run clamdscan locally with the same build of 0.103.6.) But I don't see any good way to have the server scan a whole directory residing on the client machine. Would I have to send each file one at a time? (The --fdpass option doesn't work remotely.) _______________________________________________ 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
