Hello
As it seems clamdscan always load the default clamAV config file and ignore
--config-file= (if passed)
e.g. I tried
clamdscan --verbose --config-file=/usr/local/test/clamd_custom.conf
/home/files/*
I tried to change various settings in clamd_custom.conf e.g.
DetectPUA , PhishingSignat
Hello,
Le 30/03/2022 à 14:36, Gabriel via clamav-users a écrit :
Hello
As it seems clamdscan always load the default clamAV config file and ignore
--config-file= (if passed)
e.g. I tried
clamdscan --verbose --config-file=/usr/local/test/clamd_custom.conf
/home/files/*
I tried to change var
Hi there,
On Wed, 30 Mar 2022, Gabriel via clamav-users wrote:
As it seems clamdscan always load the default clamAV config file and ignore
--config-file= (if passed)
e.g. I tried
clamdscan --verbose --config-file=/usr/local/test/clamd_custom.conf
/home/files/*
I tried to change various set
Hi Ged,
Thank you very much for the detailed reply! Could I ask more about what will
happen if ClamAV is compromised? I'm guessing it will give wrong detection
result for the malware and also for other files to be scanned, or the scanner
will crash then cannot work any more. Is there also a pro
Hi there,
On Wed, 30 Mar 2022, Yang, Jiayi via clamav-users wrote:
... what will happen if ClamAV is compromised? I'm guessing ...
It doesn't help to guess. If *anything* is compromised then you
should probably treat the entire computer to be under the control of
criminals and act according
If the purpose of doing all of this is to detect if malware is present, I would
do it outside of the sandbox. The point of a sandbox is to let malware execute
and NOT stop it.
> On Mar 30, 2022, at 11:48 AM, G.W. Haywood via clamav-users
> wrote:
>
> Hi there,
>
> On Wed, 30 Mar 2022, Yang,
