Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752495AbZAECHp (ORCPT ); Sun, 4 Jan 2009 21:07:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751768AbZAECHg (ORCPT ); Sun, 4 Jan 2009 21:07:36 -0500 Received: from tundra.namei.org ([65.99.196.166]:2857 "EHLO tundra.namei.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751105AbZAECHf (ORCPT ); Sun, 4 Jan 2009 21:07:35 -0500 Date: Mon, 5 Jan 2009 13:07:00 +1100 (EST) From: James Morris To: David Howells cc: Christoph Hellwig , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, "Serge E. Hallyn" , linux-security-module@vger.kernel.org, Stephen Rothwell Subject: Re: [PATCH] CRED: Fix regression in cap_capable() as shown up by sys_faccessat() [ver #2] In-Reply-To: <21275.1230736542@redhat.com> Message-ID: References: <24959.1230694093@redhat.com> <20081230134248.GA30124@lst.de> <21275.1230736542@redhat.com> User-Agent: Alpine 1.10 (LRH 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1048 Lines: 30 On Wed, 31 Dec 2008, David Howells wrote: > > Here's an improved patch. It differentiates the use of objective and > subjective capabilities by making capable() only check current's subjective > caps, but making has_capability() check only the objective caps of whatever > process is specified. > > It's a bit more involved, but I think it's the right thing to do. I think it's the right approach, too, and the patch seems ok to me. I've applied it to git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/security-testing-2.6#next and expect to push it to Linus in the next day or so. It's not a trivial change, and could do with more review (Serge?). It seems that more testing should be done in linux-next vs. waiting for the merge window. - James -- James Morris -- 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/