public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Lutomirski <luto@myrealbox.com>
To: Chris Wright <chrisw@osdl.org>
Cc: Olaf Dietsche <olaf+list.linux-kernel@olafdietsche.de>,
	Andy Lutomirski <luto@myrealbox.com>,
	Stephen Smalley <sds@epoch.ncsc.mil>,
	Albert Cahalan <albert@users.sourceforge.net>,
	linux-kernel mailing list <linux-kernel@vger.kernel.org>,
	Valdis.Kletnieks@vt.edu
Subject: Re: [PATCH] scaled-back caps, take 4
Date: Mon, 17 May 2004 00:19:37 -0700	[thread overview]
Message-ID: <40A86789.6030006@myrealbox.com> (raw)
In-Reply-To: <fa.gf5v6pu.c2mkrq@ifi.uio.no>

Chris Wright wrote:
> * Olaf Dietsche (olaf+list.linux-kernel@olafdietsche.de) wrote:
> 
>>Andy Lutomirski <luto@myrealbox.com> writes:
>>
>>
>>>cap_2.6.6-mm2_4.patch: New stripped-back capabilities.
>>>
>>> fs/exec.c               |   15 ++++-
>>> include/linux/binfmts.h |    9 ++-
>>> security/commoncap.c    |  130 ++++++++++++++++++++++++++++++++++++++++++------
>>> 3 files changed, 136 insertions(+), 18 deletions(-)
>>
>>[patch]
>>
>>Why don't you provide this as a configurable andycap.c module?
>>I think, this is the whole point of LSM.
> 
> 
> I agree, if we can't find a clean way to do it.  However, note this
> includes changes to core.  And it's nice to fix this for the base case.

On the other hand, this version has minimal changes to core (it adds a new 
field to linux_binprm and makes fs/exec.c fill in some extra information). 
  These changes shouldn't break any existing code, as the current behavior 
is for bprm->cap_* to be undefined when bprm_set_security is called.  None 
of this is strictly necessary for my patch, but it makes it a lot cleaner.

So, if the core changes were merged, my caps semantics could be maintained 
as a (fairly simple) separate LSM.  That prevents it working with SELinux 
or other (non-stacking) LSMs loaded.

--Andy

       reply	other threads:[~2004-05-17  7:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.id6it11.41id3h@ifi.uio.no>
     [not found] ` <fa.gf5v6pu.c2mkrq@ifi.uio.no>
2004-05-17  7:19   ` Andy Lutomirski [this message]
2004-05-17 11:59     ` [PATCH] scaled-back caps, take 4 Stephen Smalley
     [not found] <fa.i8g63r1.9jata3@ifi.uio.no>
     [not found] ` <fa.hjocttu.1cgcc3q@ifi.uio.no>
     [not found]   ` <40B0F65F.3020706@myrealbox.com>
2004-05-23 20:57     ` Olaf Dietsche
2004-05-24 16:55       ` Martin Schlemmer
     [not found] <fa.dt4cg55.jnqvr5@ifi.uio.no>
2004-05-14 16:18 ` [PATCH] capabilites, take 2 Andy Lutomirski
2004-05-14 18:07   ` Chris Wright
2004-05-14 22:48     ` [PATCH] scaled-back caps, take 4 (was Re: [PATCH] capabilites, take 2) Andy Lutomirski
2004-05-15  0:06       ` [PATCH] scaled-back caps, take 4 Olaf Dietsche
2004-05-14 22:09         ` Albert Cahalan
2004-05-15  0:27         ` Chris Wright
     [not found]       ` <20040517231912.H21045@build.pdx.osdl.net>
2004-05-18  9:11         ` [PATCH] scaled-back caps, take 4 (was Re: [PATCH] capabilites, take 2) Andy Lutomirski
2004-05-19  1:27           ` Chris Wright
2004-05-19  1:54             ` [PATCH] scaled-back caps, take 4 Andy Lutomirski
2004-05-19  7:30               ` Chris Wright
2004-05-23  9:28                 ` Andy Lutomirski
2004-05-23 18:48                   ` Olaf Dietsche

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=40A86789.6030006@myrealbox.com \
    --to=luto@myrealbox.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=albert@users.sourceforge.net \
    --cc=chrisw@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olaf+list.linux-kernel@olafdietsche.de \
    --cc=sds@epoch.ncsc.mil \
    /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