[clamav-users] Clamd instream scanning

[Micah Snyder (micasnyd)]

Hi Chad,

Some file types cannot be handled in memory, although it will keep things in memory as much as possible.

As noted in the clamd sample config:

# Optional path to the global temporary directory.
# Default: system specific (usually /tmp or /var/tmp).
#TemporaryDirectory /var/tmp

The default temp directory, if one is not specified, is system specific, and is likely to be /tmp or /var/tmp.

-Micah

From: clamav-users <clamav-users-bounces at lists.clamav.net> on behalf of "Wilson, Chad - US via clamav-users" <clamav-users at lists.clamav.net>
Reply-To: ClamAV users ML <clamav-users at lists.clamav.net>
Date: Thursday, April 4, 2019 at 12:18 PM
To: "clamav-users at lists.clamav.net" <clamav-users at lists.clamav.net>
Cc: "Wilson, Chad - US" <cwilson at caci.com>
Subject: [clamav-users] Clamd instream scanning

Knowledge needed please.

When streaming files to clamd for scanning, does the daemon write the file or does it handle all in memory?

We do not have the temp directory uncommented/specified, so IF it writes it first, where does it write to?

If it writes first, then do we have the risk of another on access scanner interrupting clamd?

If it handles all in memory, then no other questions.
Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clamav.net/pipermail/clamav-users/attachments/20190405/09528b2a/attachment.htm>