Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261290AbVALSII (ORCPT ); Wed, 12 Jan 2005 13:08:08 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261301AbVALSIH (ORCPT ); Wed, 12 Jan 2005 13:08:07 -0500 Received: from fw.osdl.org ([65.172.181.6]:56728 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S261290AbVALSF4 (ORCPT ); Wed, 12 Jan 2005 13:05:56 -0500 Date: Wed, 12 Jan 2005 10:05:34 -0800 (PST) From: Linus Torvalds To: Chris Wright cc: akpm@osdl.org, alan@lxorguk.ukuu.org.uk, marcelo.tosatti@cyclades.com, linux-kernel@vger.kernel.org Subject: Re: thoughts on kernel security issues In-Reply-To: <20050112094807.K24171@build.pdx.osdl.net> Message-ID: References: <20050112094807.K24171@build.pdx.osdl.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 866 Lines: 23 On Wed, 12 Jan 2005, Chris Wright wrote: > > This same discussion is taking place in a few forums. Are you opposed to > creating a security contact point for the kernel for people to contact > with potential security issues? This is standard operating procedure > for many projects and complies with RFPolicy. I wouldn't mind, and it sounds like a good thing to have. The _only_ requirement that I have is that there be no stupid embargo on the list. Any list with a time limit (vendor-sec) I will not have anything to do with. If that means that you can get only the list by invitation-only, that's fine. Linus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/