Closed gbot closed 7 years ago
I've only tested on one server so far, but it appears that running maldet -u
has resolved this:
maldet -u
Linux Malware Detect v1.6
(C) 2002-2017, R-fx Networks <proj@rfxn.com>
(C) 2017, Ryan MacDonald <ryan@rfxn.com>
This program may be freely redistributed under the terms of the GNU GPL v2
maldet(23035): {sigup} performing signature update check...
maldet(23035): {sigup} local signature set is version 2017041129590
maldet(23035): {sigup} new signature set (2017041410039) available
maldet(23035): {sigup} downloading https://cdn.rfxn.com/downloads/maldet-sigpack.tgz
maldet(23035): {sigup} downloading https://cdn.rfxn.com/downloads/maldet-cleanv2.tgz
maldet(23035): {sigup} verified md5sum of maldet-sigpack.tgz
maldet(23035): {sigup} unpacked and installed maldet-sigpack.tgz
maldet(23035): {sigup} verified md5sum of maldet-clean.tgz
maldet(23035): {sigup} unpacked and installed maldet-clean.tgz
maldet(23035): {sigup} signature set update completed
maldet(23035): {sigup} 12451 signatures (9721 MD5 | 1951 HEX | 779 YARA | 0 USER)
Slightly off topic here, but does running a maldet -a
scan also scan with the clamscan definitions? i.e. is running maldet like running clamscan as well?
Thanks!
@gbot good off topic question, I was wandering the same and does clamscan
benefits from maldet
rules automatically when maldet
is installed?
@gbot @milosdjakonovic This is a two way relationship; when LMD is installed it places the LMD compatible ClamAV rules inside the ClamAV signature path. As such, when LMD uses clamscan to perform scanning, it is taking advantage of all ClamAV signatures, inclusive of LMD. This is also true of manual scans with clamscan, it will take advantage of all its normal rules as well as the LMD rules, since they are located in the ClamAV signature path.
The duplicate signature issue was corrected some time back and was an upstream issue with the YARA rules and how they are published by their creators. I have since added additional checking on the rules when they are downloaded into the LMD repo to ensure the duplicates never happen again.
Thanks!
@rfxn Thanks very much for the explanation! I was sometimes repeating scans of the same path with maldet and then clamscan -- great to know that's not necessary.
Hi,
Since installing Maldet 1.6 (on Ubuntu 14.04), whenever I run a clamscan I get the following errors, server CPU and memory usage spike way up, and if I don't kill the process quickly, the server crashes.
Appears to be an issue with
var/lib/clamav/rfxn.yara
containing duplicate rules.My clamscan version is:
ClamAV 0.99.2/23297/Sat Apr 15 08:54:36 2017
When I run a foreground clamscan, such as
clamscan -ir /srv/users/username/apps/appname/public
, I get: