bugtraq - Re: Public Review of OIS Security Vulnerability Reporting and Response Guidelines

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: <874qomyw4o.fsf@deneb.enyo.de>
Date: Mon, 05 Jul 2004 23:36:23 +0200
From: Florian Weimer <fw@...eb.enyo.de>
To: OIS <announcements@...afety.org>
Cc: bugtraq@...urityfocus.com, NTBUGTRAQ@...TSERV.NTBUGTRAQ.COM,
   full-disclosure@...ts.netsys.com
Subject: Re: Public Review of OIS Security Vulnerability
 Reporting and Response Guidelines

> The Organization for Internet Safety (OIS) extends an invitation to
> the readers of the BugTraq, NTBugtraq, and Full-Disclosure mailing
> lists to participate in the ongoing public review of the OIS Security
> Vulnerability Reporting and Response Guidelines.

The definition of the term "security vulnerability" still does not
match current industry practice.  Almost all COTS software lacks a
publicly reviewable design document, and popular software has not been
designed for Internet security *at* *all*.  In a few cases, this is
even acknowledged by the vendor (think of Microsoft Windows Me or
Microsoft Windows NT).

In fact, I can't think of any recent, critical vulnerability that
matches your definition of a vulnerability.

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html