-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Steve Basford wrote: > > Christopher X. Candreva wrote: >> In my experience, it means a database maintainer who made a >> simple mistake in one line. >> > I don't think this'll really add anything useful to the > discussion.... but I've seen that happen in one of the mrsbl > databases.. but there are some small things the non-ClamAV Team > database maintainers can do to avoid it: > > I test my databases before I send them out like this: > > clamscan -d c:\clamav~1\share\clamav\phish.ndb phish_sigtest.txt > clamscan -d c:\clamav~1\share\clamav\scam.ndb scam_sigtest.txt > > If either give errorlevel 50... then I don't bother creating the > gzipped version of the database for upload :) > > I guess that means end-users only then have to gzip test their > downloaded file to see if it's survived the trip over the > internet.... ie... gzip --test phish.ndb.gz. If it's errorlevel 1 > then you've got a problem, otherwise you can unzip! > > The unzip testing is a good idea... as I managed to upload a 0 byte > phish.ndb.gz file, due to an odd firewall bug, which meant that my > ftp host only received a 0 byte file :( > > Cheers, > > Steve I've seen the same on MSRBL-Images. Seems to be broken lately. I always run (well, the script does) clamscan -d var/tmp/<<database>> before installing them, which prevents corrupt db's, though it doesn't prevent incomplete db's :-(
Kind regards, Sander Holthaus -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) iD8DBQFFlpK4Vf373DysOTURApXeAKDDKZVIo9wk8LJqT+1JrJgPG3t2CACgrB6b PyzcljGryqiKCLcWePaWD84= =ymCW -----END PGP SIGNATURE----- _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
