Hello again,
On Mon, 7 Nov 2022, An Schall via clamav-users wrote:
the command we are using is:
sudo -H clamdscan -v -c /etc/clamd.d/scan.conf --multiscan --fdpass
Try it without '--fdpass'. What do you mean the '-H' to do for you?
[Micah, I've just noticed that '-c file' doesn't appear in
Hi there,
the command we are using is:
sudo -H clamdscan -v -c /etc/clamd.d/scan.conf --multiscan --fdpass
We do see the errors in /var/log/clamdscan.log as defined in the
configuration file /etc/clamd.d/scan.conf (see below). The exact error
messages are as follows:
Mon Nov 7 13:50:21 2022 ->
On Mon, 7 Nov 2022 at 08:39, Al Varnell via clamav-users <
clamav-users@lists.clamav.net> wrote:
> Those are vulnerability signatures, not necessarily for any existing
> malware. Anything that attempts to exploit those vulnerabilities should be
> caught.
>
Noted with thanks.
Mr. Turritopsis Dohr
Hi there,
On Mon, 7 Nov 2022, An Schall via clamav-users wrote:
we do have 2 workstations running RHEL 8 and clamav / clamd using an
identical software stack / configuration. In particular we integrate
the clamav packages via the RHEL EPEL repos. So far we have been using
0.103.6-1.el8 without
Hi all,
we do have 2 workstations running RHEL 8 and clamav / clamd using an
identical software stack / configuration. In particular we integrate
the clamav packages via the RHEL EPEL repos. So far we have been using
0.103.6-1.el8 without any issues. We have started upgrading to
0.103.7-1.el8 on o