I'm behind the Clam team in that they focus on getting sigs out before worrying about the name.
I don't know if this is a technical limitation of the virus db's (and not sure if this has been mentioned previously, sorry) but what's to stop the name of the virus being changed in the virus db once a 'common' name has been determined?
My problem with doing that is that it requires a developer to update the DB when he could be busy beating the pants off Sophos analysing new wild viruses, and frankly I'd rather live with an AKA and have up-to-the-minute protection than wait a couple of hours until the other AV's have had their little waffle about cool names. ;)
I'd prefer to adopt the approach of letting the Clam team get a def out with any name they want and have a non-developer publish basic virus info on an area of the Clam site, and on that page you'd just have the blurb on "SomeFool.Q" for example, along with a short description (only brief, tho, there's plenty of viral analysis on other sites) of the virus with an "Also known as: NetSky.Q, SmellyVirus.1, Whatever.Q", etc.
I forget now, but someone had posted a brief list of AKA's, perhaps it can be integrated into the Clam website, or a new section created on clamav.net?
It would free-up the developers from having to think about common names, it would only take a couple of Clam admins to update it after doing some queries with other AV's, and all you'd need to do is direct your end-users to the virus info page so they can find out for themselves what SomeFool is according to the other AV's.
Stuart.
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
