Adam Gibson wrote:
> Gary V wrote:
>> (have not tried it though). Make sure your update script is a recent
>> one that tests the downloads before employing them and consider
>
> This is one of the most important steps IMHO. I would make sure the
> script tests the dat files before copying them into place. The scripts
> that I have used over the years tests the dat files with the eicar virus
> test pattern to make sure they work before copying them into place.
This issue here is not whether the virus signature files work or not, it's
whether one of them is corrupted or not. A corrupted signature file will cause
clamd to silently crash and no longer be available for message scanning. The
test that needs to be done on ClamAV signature files:
clamscan --quiet -d /path/to/sigfile
will detect corrupted signature files, and thus can prevent them from being
moved into the production directory. Most, if not all, of the download scripts
available on the SaneSecurity site
(http://www.sanesecurity.com/clamav/usage.htm) enable this testing prior to
usage.
Bill
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
