| 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
| ||
|
Message-ID: <200408101447.i7AEl5S9000720@turing-police.cc.vt.edu> From: Valdis.Kletnieks at vt.edu (Valdis.Kletnieks@...edu) Subject: (no subject) On Tue, 10 Aug 2004 02:02:23 EDT, Todd Burroughs said: > No shit. They should at least get together and come up with some common > naming convention. They need to make some common "naming authority", it's > not difficult, we do it all the time with other software and as mentioned, > in all scientific disciplines. Software gets named over days/weeks. They crank out a new name for an element every few years. These things need names in *MINUTES* - often while the various A/V companies are looking at different copies of a polymorphic, multi-attack piece of malware. 5 blind men and an elephant time... and you want them to agree on a name before they even agree they're looking at the same thing??? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 226 bytes Desc: not available Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20040810/797f8a42/attachment.bin
Powered by blists - more mailing lists