From: Chris Wright <chrisw@osdl.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Serge E. Hallyn" <serue@us.ibm.com>,
Chris Wright <chrisw@osdl.org>, Andrew Morton <akpm@osdl.org>,
Stephen Smalley <sds@epoch.ncsc.mil>,
James Morris <jmorris@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] properly split capset_check+capset_set
Date: Tue, 4 Jan 2005 15:23:17 -0800 [thread overview]
Message-ID: <20050104152317.B2357@build.pdx.osdl.net> (raw)
In-Reply-To: <1104857632.17166.35.camel@localhost.localdomain>; from alan@lxorguk.ukuu.org.uk on Tue, Jan 04, 2005 at 10:03:59PM +0000
* Alan Cox (alan@lxorguk.ukuu.org.uk) wrote:
> On Maw, 2005-01-04 at 16:27, Serge E. Hallyn wrote:
> > The attached patch removes checks from kernel/capability.c which are
> > redundant with cap_capset_check() code, and moves the capset_check()
> > calls to immediately before the capset_set() calls. This allows
> > capset_check() to accurately check the setter's permission to set caps
> > on the target. Please apply.
>
> Why does this help ?
Without this change, the check was done without knowing who the target
really was, so the code that sets it had to check as well.
> A partial failure now returns no error ?
It never did. Now it behaves the same as signal delivery which returns
success if any signals were delivered, and failure if none were delivered.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2005-01-04 23:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-04 16:27 Serge E. Hallyn
2005-01-04 20:15 ` Chris Wright
2005-01-04 21:55 ` Stephen Smalley
2005-01-04 22:03 ` Alan Cox
2005-01-04 23:23 ` Chris Wright [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-15 19:48 [PATCH] Properly " Serge E. Hallyn
2004-12-15 20:34 ` Stephen Smalley
2004-12-15 23:22 ` Serge E. Hallyn
2004-12-15 23:47 ` Chris Wright
2004-12-16 16:16 ` Serge E. Hallyn
2004-12-15 23:26 ` Chris Wright
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050104152317.B2357@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sds@epoch.ncsc.mil \
--cc=serue@us.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®