On Jan 3, 2020, at 00:00, G.W. Haywood wrote:
> Please define "suddenly".
Suddenly means that the scan on December 17th took about two hours:
Time: 7569.856 sec (126 m 9 s)
and the next scan, on December 24th took about nine hours:
Time: 35785.296 sec (596 m 25 s)
Both scans used:
Eng
Hello,
Le 03/01/2020 à 00:06, G.W. Haywood via clamav-users a écrit :
Hi there,
On Thu, 2 Jan 2020, J.R. via clamav-users wrote:
All good :-) Going to remove javascript.ndb too. Sorry again.
Rather than deleting entire signature databases because of one false
positive, why don't you either:
I am running clamav 0.102.1 built with llvm enabled but I have set up a
dedicated user id called clamav(n). Then I create a shell script to run clamd
and freshclam as daemons using this clamav(n) user id. I run clamdscan for one
user and it takes only ten minutes to run. My OS is Catalina 10.15.
Hi there,
On Thu, 2 Jan 2020, Tom Ossman via clamav-users wrote:
... a central server where clamd is running and a remote client
where I have clamd.conf pointed to the central server, I can run
clamdscan on the remote client, it scans and finds the test file I
have created on it. I am now tryi
Hi there,
On Thu, 2 Jan 2020, J.R. via clamav-users wrote:
All good :-) Going to remove javascript.ndb too. Sorry again.
Rather than deleting entire signature databases because of one false
positive, why don't you either:
1. Whitelist the file (if it's static)
or
2. Whitelist the signature(
> All good :-) Going to remove javascript.ndb too. Sorry again.
Rather than deleting entire signature databases because of one false
positive, why don't you either:
1. Whitelist the file (if it's static)
or
2. Whitelist the signature(s)
Both are a quick google search and very easy to do...
__
Hello,
I'm hoping someone can help me. I have ClamAV setup in network mode in an
AWS environment on two EC2 instances. I have a central server where clamd
is running and a remote client where I have clamd.conf pointed to the
central server, I can run clamdscan on the remote client, it scans and
Thx G.W. and J.R for your answers.
Yes i deleted the line in /etc/clamav/freshclam.conf ~2 weeks ago already,
before it was:
DatabaseMirror db.local.clamav.net
DatabaseMirror database.clamav.net
DatabaseCustomURL http://www.securiteinfo.com/get/signatures/(removed for
mailing list)/securiteinfo
Hi there,
On Thu, 2 Jan 2020, i...@schroeffu.ch wrote:
... custom signatures file securiteinfohtml.hdb in ClamAV with false
positives, so I deleted the file /var/lib/clamav/securiteinfohtml.hdb
and restarted clamav (freshclam, clamd). But ClamAV seems still
using this signature DB, it is still
> How do I purge a CustomDatabaseURL correctly?
Did you remove that DB from your FreshClam config and / or
clamav-unofficial-signatures script so it won't re-download it?
___
clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.
Hi ClamAV Geeks,
i have had the custom signatures file securiteinfohtml.hdb in ClamAV with false
positives, so I deleted the file /var/lib/clamav/securiteinfohtml.hdb and
restarted clamav (freshclam, clamd). But ClamAV seems still using this
signature DB, it is still detecting viruses from this
Hi there,
On Thu, 2 Jan 2020, Michael Newman via clamav-users wrote:
ClamAV 0.102.1/25679/Mon Dec 30 17:01:01 2019
macOS 10.15.2
Help me figure out why clamscan is suddenly taking so long.
...
Engine version: 0.100.1
Total errors: 1
Time: 8728.307 sec (145 m 28 s)
...
Engine version: 0.102.1
T
12 matches
Mail list logo
