-
Notifications
You must be signed in to change notification settings - Fork 246
Open
Description
# Remote clamd support
# If you're running a dedicated clamd server, you can instruct clamdscan to use
# it instead of the local daemon (which doesn't even need to run). To use
# this you need to create a 'clamd.remote.conf' with:
#
# TCPSocket 3310
# TCPAddr clamd.example.com
#
# Enable connecting to a remote clamd service to conduct all file scanning
# offload from local system. This requires that clamdscan binary be available
# to the local system.
#
# Files being scanned are effectively piped to remote daemon, this can be very
# bandwidth intensive.
# [ 0 = disabled, 1 = enabled ]
scan_clamd_remote="1"
# To instruct maldetect to use that config, enter the path to that file:
remote_clamd_config="/etc/clamd.d/clamd.remote.conf"
the following code is not working
maldet is not activating/triggering remote clamav
However, if for example you run manually just clamav with the same:
clamdscan --config-file=/etc/clamd.d/clamd.remote.conf /var/www/html/
This is working properly. So it looks like maldet is not calling this properly.
maldet version v1.6.6 is used
Metadata
Metadata
Assignees
Labels
No labels