full-disclosure - Re: Asynchronous, industry-wide virus naming scheme proposed

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 for Android: free password hash cracker in your pocket

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

Message-ID: <freemail.20030902160617.34054@fm9.freemail.hu>
From: etomcat at freemail.hu (Feher Tamas)
Subject: Re: Asynchronous, industry-wide virus naming scheme proposed

Hello,

>Interesting post... one thing tho, those root "VNS" servers will 
>instantly be the target of DDoS attack by the virus writers...

As the root-VNS server need not serve end users, only the vendor-VNS 
and maybe vendor-reseller-VNS servers, they could drop any packet 
not coming from trusted IP addesses or just use data transmit line that 
are not part of the internet.

Protecting vendor-VNS servers against DDoS is up to each AV-vendor, 
e.g. they could rent massive capacity at Akamai.net or other huge 
datapipe provide. FYIF, McAfee (NAI) already uses Akamai to distribute 
its virus signature database updates.

>But I think its a problem that has a non-technological
>solution, if any solution is possible.

Indeed my proposal may be way over-complicated, but I do feel virus 
naming must be technology-assisted. Else it will never be uniform and 
crackers will reign over the confusion, while innocent, hex-illiterate 
computer users continue to suck.

Sincerely: Tamas Feher.