Folks, just for the record, this problem was cleared up when I upgraded to clamAV-0.95 from ver. 0.92.1
So it's pretty clear that early versions cannot handle what someone referred to as "newish" db files. -john >Does anyone have an idea why the following 2 Sane Security Defs (used >within ClamAV) are consistently (since I have started using them) >failing the integrity test ? > >I'm not sure if this is the best place to address this issue but I >imagine others here are seeing this too. > >-john > > >Testing updated database file: spam.ldb >gpg: Signature made Wed Apr 01 06:58:42 2009 PDT using DSA key ID 31EA4D9E >gpg: Good signature from "Sanesecurity (Sanesecurity Signatures) ><steveb_cla...@sanesecurity.co.uk>" >Clamscan reports spam.ldb database integrity tested BAD - SKIPPING > >Testing updated database file: sanesecurity.ftm >gpg: Signature made Fri Mar 20 12:18:25 2009 PDT using DSA key ID 31EA4D9E >gpg: Good signature from "Sanesecurity (Sanesecurity Signatures) ><steveb_cla...@sanesecurity.co.uk>" >Clamscan reports sanesecurity.ftm database integrity tested BAD - SKIPPING > >-- >John Goubeaux >Systems Administrator >Gevirtz Graduate School of Education >UC Santa Barbara >Phelps Hall 3534 >805 893-8190 >_______________________________________________ >Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net >http://www.clamav.net/support/ml -- John Goubeaux Systems Administrator Gevirtz Graduate School of Education UC Santa Barbara Phelps Hall 3534 805 893-8190 _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
