Re: Proper procedure for reporting possible security vulnerabilities?

[Chris Wright <chrisw@osdl.org>]

* Jesper Juhl (juhl-lkml@dif.dk) wrote:
> 
> This thread got started by a question about how to go about informing 
> people about security vulnerabilities so I think we should erhaps try to 
> provide some sensible information about how to go about that that can be 
> useful to people no matter what "disclosure camp" the agree with. How 
> about something like what I've written below as an addition to 
> REPORTING-BUGS or as a seperate REPORTING-SECURITY-BUGS document ?

Let's just bite the bullet...

===== REPORTING-BUGS 1.2 vs edited =====
--- 1.2/REPORTING-BUGS	2002-02-04 23:39:13 -08:00
+++ edited/REPORTING-BUGS	2005-01-10 15:35:10 -08:00
@@ -16,6 +16,9 @@ code relevant to what you were doing. If
 describe how to recreate it. That is worth even more than the oops itself.
 The list of maintainers is in the MAINTAINERS file in this directory.
 
+      If it is a security bug, please copy the Security Contact listed
+in the MAINTAINERS file.  They can help coordinate bugfix and disclosure.
+
       If you are totally stumped as to whom to send the report, send it to
 linux-kernel@vger.kernel.org. (For more information on the linux-kernel
 mailing list see http://www.tux.org/lkml/).
===== MAINTAINERS 1.269 vs edited =====
--- 1.269/MAINTAINERS	2005-01-10 17:29:35 -08:00
+++ edited/MAINTAINERS	2005-01-11 13:29:23 -08:00
@@ -1959,6 +1959,11 @@ M:	christer@weinigel.se
 W:	http://www.weinigel.se
 S:	Supported
 
+SECURITY CONTACT
+P:	Security Officers
+M:	kernel-security@{osdl.org, vger.kernel.org, wherever}
+S:	Supported
+
 SELINUX SECURITY MODULE
 P:	Stephen Smalley
 M:	sds@epoch.ncsc.mil