> -----Original Message----- > From: clamav-users-boun...@lists.clamav.net [mailto:clamav-users- > boun...@lists.clamav.net] On Behalf Of Tomasz Kojm > Sent: Wednesday, May 20, 2009 12:39 PM > To: clamav-users@lists.clamav.net > Subject: Re: [Clamav-users] Deletion of local.ign > > the .ign database was designed with the ClamAV db maintainers > and not users in mind. It allows us to disable specific signatures > in main.cvd until a new version is published. It requires this precise > information about target signatures for two reasons: safety > and speed. By requiring the line numbers and signature names > the whitelisting mechanism is more resistant to errors (which > could have really bad consequences) but also doesn't slow down > loading of the databases (because we use the line numbers > as the main filter). > > I don't know what your script has to do with the .ign databases > but believe it would be much more effective and easier to implement > any workarounds in the script instead of the clamav engine. >
Would there be any harm in having the hash as another parameter in the .ign file? It seems like a minor adjustment in parsing for the clam code would allow more flexibility and automation on the admin side. Alternatively, since .ign "was designed with the ClamAV db maintainers and not users in mind", should a new .ign-type file be created with users/admins in mind? Jason A. Bertoch Network Administrator ja...@electronet.net Electronet Broadband Communications 3411 Capital Medical Blvd. Tallahassee, FL 32308 (V) 850.222.0229 (F) 850.222.8771 _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
