From: Chris Wright <chrisw@osdl.org>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: Chris Wright <chrisw@osdl.org>,
Andy Lutomirski <luto@myrealbox.com>,
Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
James Morris <jmorris@redhat.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: compute_creds fixup in -mm
Date: Wed, 21 Apr 2004 11:54:11 -0700 [thread overview]
Message-ID: <20040421115411.M22989@build.pdx.osdl.net> (raw)
In-Reply-To: <1082572971.9213.75.camel@moss-spartans.epoch.ncsc.mil>; from sds@epoch.ncsc.mil on Wed, Apr 21, 2004 at 02:42:51PM -0400
* Stephen Smalley (sds@epoch.ncsc.mil) wrote:
> On Wed, 2004-04-21 at 14:28, Chris Wright wrote:
> > * Stephen Smalley (sds@epoch.ncsc.mil) wrote:
> > > I didn't see Chris' patch. I assume that the worst case is unexpected
> > > program failure due to lack of capability, right? The SELinux security
> >
> > The opposite. You'd get a program with non-root euid, but full
> > capability set, and AT_SECURE set false. My patch is below.
>
> Sorry, I wasn't clear. I meant the worst case due to the share/ptrace
> state check being duplicated in SELinux and in commoncap, as opposed to
> being performed once as in Andy's patch.
Ah, indeed.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2004-04-21 18:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040421010621.L22989@build.pdx.osdl.net>
2004-04-21 17:27 ` Andy Lutomirski
2004-04-21 18:13 ` Stephen Smalley
2004-04-21 18:28 ` Chris Wright
2004-04-21 18:42 ` Stephen Smalley
2004-04-21 18:54 ` Chris Wright [this message]
2004-04-21 19:37 ` Andy Lutomirski
2004-04-21 20:10 ` Stephen Smalley
2004-04-21 19:07 ` Chris Wright
[not found] <fa.n7n31hd.1k7ce37@ifi.uio.no>
[not found] ` <fa.f9m11dm.206fg4@ifi.uio.no>
2004-04-21 20:36 ` Andy Lutomirski
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=20040421115411.M22989@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=akpm@osdl.org \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@myrealbox.com \
--cc=sds@epoch.ncsc.mil \
--cc=torvalds@osdl.org \
/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®