My solution to this was to remove the offending file from clamav-unofficial-sigs control file.
Change /etc/clamav-unofficial-sigs/master.conf to comment out the offending line:
#Antidebug_AntiVM/antidebug_antivm.yar|LOW # anti debug and anti virtualization techniques used by malware
and of course remove installed files. I had the advantage of compiling my own version of clamav and then could back up easily. This is not that easy of you are using yum packaged releases.
However, it is the case that if 100.0 is released for EPEL and used on systems where this file is installed - then clamd will just die.. and the ensuing complaint levels may not be good. Sadly it will look like a fault in clamd - and actually we are used to having faultless releases from you guys.
My solution to this was to remove the offending file from clamav- unofficial- sigs control file.
Change /etc/clamav- unofficial- sigs/master. conf to comment out the offending line:
#Antidebug_ AntiVM/ antidebug_ antivm. yar|LOW # anti debug and anti virtualization techniques used by malware
and of course remove installed files. I had the advantage of compiling my own version of clamav and then could back up easily. This is not that easy of you are using yum packaged releases.
However, it is the case that if 100.0 is released for EPEL and used on systems where this file is installed - then clamd will just die.. and the ensuing complaint levels may not be good. Sadly it will look like a fault in clamd - and actually we are used to having faultless releases from you guys.