bugtraq - Re: defining 0day

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: <500BE702-BB9B-47E8-A96F-AD6B67C0B408@pastiche.org>
Date: Wed, 26 Sep 2007 06:40:52 +1000
From: Charles Miller <cmiller@...tiche.org>
To: Gadi Evron <ge@...uxbox.org>
Cc: bugtraq@...urityfocus.com, full-disclosure@...ts.grok.org.uk
Subject: Re: defining 0day

On 26/09/2007, at 5:02 AM, Gadi Evron wrote:

> Okay. I think we exhausted the different views, and maybe we are  
> now able to come to a conlusion on what we WANT 0day to mean.
>
> What do you, as professional, believe 0day should mean, regardless  
> of previous definitions?

As a professional, I would be happy to see terms like '0day' banished  
from the lexicon entirely. It's an essentially meaningless -- all  
third-party exploits are zero-day to _somebody_ -- term of boast co- 
opted from the warez scene, and we can do perfectly well without it.

Quibbling over its precise definition seems a ridiculous waste of bytes.

C