Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261570AbVAGT5R (ORCPT ); Fri, 7 Jan 2005 14:57:17 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261580AbVAGT42 (ORCPT ); Fri, 7 Jan 2005 14:56:28 -0500 Received: from mail.joq.us ([67.65.12.105]:48838 "EHLO sulphur.joq.us") by vger.kernel.org with ESMTP id S261548AbVAGTzJ (ORCPT ); Fri, 7 Jan 2005 14:55:09 -0500 To: Martin Mares Cc: Chris Wright , Paul Davis , Christoph Hellwig , Arjan van de Ven , Lee Revell , Ingo Molnar , Alan Cox , Linux Kernel Mailing List , Andrew Morton Subject: Re: [PATCH] [request for inclusion] Realtime LSM References: <20050107162902.GA7097@ucw.cz> <200501071636.j07Gateu018841@localhost.localdomain> <20050107170603.GB7672@ucw.cz> <20050107092918.B2357@build.pdx.osdl.net> <20050107173229.GA9794@ucw.cz> From: "Jack O'Quin" Date: Fri, 07 Jan 2005 13:55:33 -0600 In-Reply-To: <20050107173229.GA9794@ucw.cz> (Martin Mares's message of "Fri, 7 Jan 2005 18:32:29 +0100") Message-ID: <87y8f5580a.fsf@sulphur.joq.us> User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Corporate Culture, linux) 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: 811 Lines: 23 Martin Mares writes: >> Yes, SETPCAP became a gaping security hole. Recall the sendmail hole. > > Hmmm, I don't remember now, could you give me some pointer, please? I already did that... > Jack O'Quin wrote: > > The biggest problem was CAP_SETPCAP, which for good reasons[1] is > > disabled in distributed kernels. This forced every user to patch and > > build a custom kernel. Worse, it opened all our systems up to the > > problems reported by this sendmail security advisory. [1] http://www.securiteam.com/unixfocus/5KQ040A1RI.html -- joq - 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/