bugtraq - Re: Funny article

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: <Pine.LNX.4.44.0311141047090.4764-100000@ganymede.bcc.local>
Date: Fri, 14 Nov 2003 10:52:07 +1100 (EST)
From: Systems Administrator <sysadmin@...et.com.au>
To: "Steven M. Christey" <coley@...re.org>
Cc: bugtraq@...urityfocus.com
Subject: Re: Funny article


	Quick question: would it make sense to have somewhere:

-	A common (computer/human readable) format for vulnerability 
	disclosures
-	A common format for bugfix publications

	?

	I was thinking something like:

Software name: foo-package
Software version: 2.4-2.6,3.1
Vulnerability type: ...
.
.
.

	And also some documentation on how to fill in each (eg. 
vulnerability type)?  And specify that these be text attachments to 
e-mails, or something, so that computers can read them, and people can 
read them, and it'll make everything easy.  

	Is there something like this already, or another forum where I 
should be asking this instead?  

	:)

-- 
Tim Nelson
Systems Administrator
Sunet Internet
Tel: +61 3 5241 1155
Fax: +61 3 5241 6187
Web: http://www.sunet.com.au/
Email: sysadmin@...et.com.au