We've been tossing this back and forth here at the office and we think we may have a solution. Let us keep bouncing it around some more and we'll get something out to you soon.
On Sun, Feb 12, 2012 at 4:22 AM, Al Varnell <alvarn...@mac.com> wrote: > On 2/11/12 5:52 PM, "Greg Cirino" <gcir...@cirelle.com> wrote: > > > I'm not sure there is much value to the virusdb updates, as I usually > > delete them, except to see if my submission made it. > > > > I've tried to figure out what is being caught, and there is always some > > esoteric name that rarely coincides with commonly held virus names. > > > > Not sure if it's a patent on the name thing or what. > > > I find this to be an industry-wide problem not necessarily unique to > clamav. > Part of it is the overlap between malware classifications. Some of it is > probably in the interest of getting definitions out-the-door without a lot > of research. It drives end-users crazy when they get an infection name that > is totally unique to clamav and there is no information about what it is, > what it does and how to get rid of any extended infection. > > > -Al- > > -- > Al Varnell > Mountain View, CA > > > > _______________________________________________ > Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net > http://www.clamav.net/support/ml > -- Joel Esler Senior Research Engineer, VRT OpenSource Community Manager Sourcefire _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
