full-disclosure - AV Naming Convention

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <00f601c47f00$291201b0$fc11010a@msad.brookshires.net>
From: toddtowles at brookshires.com (Todd Towles)
Subject: AV Naming Convention

So if I change my name the police can't find me? ;)

AV companies should be able to work with any form of ID. Use their local
until an agreement as been made. 

-----Original Message-----
From: full-disclosure-admin@...ts.netsys.com
[mailto:full-disclosure-admin@...ts.netsys.com] On Behalf Of Thomas Loch
Sent: Tuesday, August 10, 2004 11:09 AM
To: full-disclosure@...ts.netsys.com
Subject: Re: [Full-Disclosure] AV Naming Convention

> This completely misses the point.
I do not completely agree ...

> When a new virus is discovered, it is 
> essential that there is a RAPID response to the threat. ...
I agree...

> ...The idead of 
> handing the critter over to a committee to decide it's name is, quite
> frankly, plain bonkers.
Why?

Why can't we handle not yet named viruses as 'unnamed' or we use a 
standardized (by ISO?) method to generate a numeric code that consists of a 
classification in categories and a sequential number and probably some kind 
of checksum or hash until the virus gets an official name?

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html