full-disclosure - 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]

Date: Sat, 19 Apr 2008 17:10:22 -0700
From: coderman <coderman@...il.com>
To: n3td3v <xploitable@...il.com>
Cc: n3td3v <n3td3v@...glegroups.com>, full-disclosure@...ts.grok.org.uk,
	Gadi Evron <ge@...uxbox.org>
Subject: Re: defining 0day

On Sat, Apr 19, 2008 at 5:02 PM, n3td3v <xploitable@...il.com> wrote:
> ...
>  It doesn't matter how old it is, as long as no patch is available, it
>  will always come out of no where and pwn your ass.

again you show your ignorance.

if you are aware of the risk, there are a multitude of mitigations,
outside of official vendor patches.  these range from firewall /
packet filter, to applications configuration changes, to third party
patches, to alternate implementations, etc.

if you are aware of the vulnerability, it is no longer 0day.

if you get pwned by a known vuln, that is your laziness or stupidity at fault.

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/