full-disclosure - Why Vulnerability Databases can't do everything

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: <20050716081734.GC14646@sivokote.iziade.m$>
Date: Sat Jul 16 09:16:43 2005
From: guninski at guninski.com (Georgi Guninski)
Subject: Why Vulnerability Databases can't do everything

On Fri, Jul 15, 2005 at 02:35:52PM -0400, Steven M. Christey wrote:
> 
> In addition, vulnerability databases and notification services have
> to:
>

(7) be responsible and ethical, without being whores [1]. 
(8) help make the infidels responsible and ethical.



[1]
http://www.whitehats.ca/main/about_us/policies/draft-christey-wysopal-vuln-disclosure-00.txt
Steve Christey
INTERNET-DRAFT                                                     MITRE
Valid for six months                                       Chris Wysopal
Category: Best Current Practice                             @stake, Inc.
                                                           February 2002

              Responsible Vulnerability Disclosure Process
             draft-christey-wysopal-vuln-disclosure-00.txt
 

-- 
where do you want bill gates to go today?