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  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]
From: thomas8142 at (Thomas Loch)
Subject: 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 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?

Powered by blists - more mailing lists