Good Morning too all!
I’m having an issue whereas clamp is quitting unexpectedly and I have no clue
what is causing this. There is not trace in the logs.
I had thought it was due to space issues in /tmp as my tmp is only 500MB and it
was full of clam files.
I changed the clams.conf to read:
As well as mail scanning, we use CLAMAV with HAVP for HTTP scanning.
Although HAVP is not currently being developed, it seems to work OK.
P.S. HAVP uses the CLAMAV library directly to do the scanning, rather
than CLAMD or (worse) CLAMSCAN.
On Tue, 13 Jun 2017 09:37:36 +
Paul Moreno wrote:
Hi there,
On Jun 13, 2017, at 06:53, Paul Moreno wrote:
I'm in the process of providing a recommendation to a client on the
use of ClamAV. ...
As it stands now, the client get massive amounts of false
positives with seemingly no trigger. I'm working on sifting
through log files to see if the
On Tue, Jun 13, 2017 at 09:37:36AM +, Paul Moreno wrote:
> Hi All,
>
> I'm in the process of providing a recommendation to a client on the use of
> ClamAV. From what I've read in various forums and online material, ClamAV
> appears to be better suited for mail systems, such as postfix, and Wi
I'll request permission to get some sanitised data.
From: clamav-users on behalf of Joel
Esler (jesler)
Sent: Tuesday, June 13, 2017 13:07
To: ClamAV users ML
Subject: Re: [clamav-users] Use on linux operating systems
Cause you provide five examples? So we c
Cause you provide five examples? So we can see if it's one particular error?
--
Sent from my iPhone
> On Jun 13, 2017, at 07:02, Paul Moreno wrote:
>
> There are so many it's proven difficult to recommend the use of ClamAV.
>
>> On 13 Jun 2017, at 12:57, Joel Esler (jesler) wrote:
>>
>> Pl
It might be possible to reduce those with simple changes to the configuration
parameters, if we knew more about them.
-Al-
On Tue, Jun 13, 2017 at 04:01 AM, Paul Moreno wrote:
>
> There are so many it's proven difficult to recommend the use of ClamAV.
>
>> On 13 Jun 2017, at 12:57, Joel Esler
There are so many it's proven difficult to recommend the use of ClamAV.
> On 13 Jun 2017, at 12:57, Joel Esler (jesler) wrote:
>
> Plus reports of those false positives would be fantastic.
>
> --
> Sent from my iPhone
>
>> On Jun 13, 2017, at 06:53, Paul Moreno wrote:
>>
>> Thanks for the r
Plus reports of those false positives would be fantastic.
--
Sent from my iPhone
> On Jun 13, 2017, at 06:53, Paul Moreno wrote:
>
> Thanks for the responses. As it stands now, the client get massive amounts
> of false positives with seemingly no trigger. I’m working on sifting through
> l
Thanks for the responses. As it stands now, the client get massive amounts of
false positives with seemingly no trigger. I’m working on sifting through log
files to see if there’s a reason for it or if this specific environment isn’t
suited to use this as a scanner.
-Paul
> On 13 Jun 2017,
If your Linux systems are on network segments co-hosting windows devices or
sharing files/filesystems, running Clamscan helps prevent having your Linux
clients hosting viruses for your windows machines or meeting
standards/requirements such as SI-3 in NIST 800-53.
We run it on our entry/exit point
Thanks Al, there's actually far more than that. Wonder how many signatures I
have written that start with ELF or even APK.
--
Sent from my iPhone
> On Jun 13, 2017, at 06:10, Al Varnell wrote:
>
> Although ClamAV was originally introduced as mail scanner and does have some
> unique capabil
Although ClamAV was originally introduced as mail scanner and does have some
unique capabilities there, it has progressed far beyond that over the years.
I can't give you any personal Linux or Unix experience, so I'll leave that to
others, but I can tell you that today their are signatures for 2
Hi All,
I'm in the process of providing a recommendation to a client on the use of
ClamAV. From what I've read in various forums and online material, ClamAV
appears to be better suited for mail systems, such as postfix, and Windows
hosts. Can anyone comment on the reliability and accuracy of
14 matches
Mail list logo
