Ravi wrote:
Thanks Kris for your comments. Currently we scan the incoming
files(zips/archives) placed on the local hard drive with the
clamdscan(which uses clamd daemon), Can you share more info on what you
meant on handling the result differently if we are using the clamdscan?
Whatever calls c
Thanks Kris for your comments. Currently we scan the incoming
files(zips/archives) placed on the local hard drive with the
clamdscan(which uses clamd daemon), Can you share more info on what you
meant on handling the result differently if we are using the clamdscan?
Thanks
Ravi
On Tue, Nov 7, 201
Ravi wrote:
Hi,
Looking forward for comments and suggestions for the below reported issue
from the community.
Well, to answer your original question, it looks to me like the test is
doing exactly what it's supposed to. Core dumps would quite reasonably
contain executable chunks, but may not
Hi,
Looking forward for comments and suggestions for the below reported issue
from the community.
Thanks
Ravi
On Oct 27, 2017 4:09 PM, "Ravi" wrote:
> Hi,
>
> We are seeing instances when customer uploads his zip files which contains
> core files/core dumps during scanning ClamAV is treating s
Hi,
We are seeing instances when customer uploads his zip files which contains
core files/core dumps during scanning ClamAV is treating some of them as
“Heuristics.Broken.Executable FOUND”. Currently we have turned-on this
check in the clamd.conf as below.
*# With this option clamav will try to d
