Sandeep Talla wrote:
Hi Mark/Kris,
Thank you for your responses. I have placed the *fireeye.ldb* file under
the directory /var/lib/clamav/ and modified the permission to 644 and
ownership to clamav. Then we have restarted the service
Clamav-Deamon and then started clamscan. However, Clamscam is not
picking up the *fireeye.ldb* file when we verify the Freshclam.log and
clamav.log files.
Are there any configuration settings that need to add for *clamd.conf*
or *freshclam.conf* in order to pick up the fireeye.ldb file during
clamscan?
The only thing that comes to mind is to check for the
"OfficialDatabaseOnly" option in the configuration; if set to "on" or
"yes" this only loads the official databases.
The output from clamscan -D might tell you more.
I have a couple of system using third party and local signatures without
problem just by dropping the files beside the stock files.
-kgd
_______________________________________________
clamav-users mailing list
[email protected]
https://lists.clamav.net/mailman/listinfo/clamav-users
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml
