All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: Manfred Georg <mgeorg@arl.wustl.edu>
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] capabilities not inherited
Date: Wed, 8 Jun 2005 13:44:30 -0700	[thread overview]
Message-ID: <20050608204430.GC9153@shell0.pdx.osdl.net> (raw)
In-Reply-To: <Pine.GSO.4.58.0506081513340.22095@chewbacca.arl.wustl.edu>

* Manfred Georg (mgeorg@arl.wustl.edu) wrote:
> I was working with passing capabilities through an exec and it
> didn't do what I expected it to.  That is, if I set a bit in
> the inherited capabilities, it is not "inherited" after an
> exec().  After going through the code many times, and still not
> understanding it, I hacked together this patch.  It probably
> has unforseen side effects and there was probably some
> reason it was not done in the first place.

True to both.  If you'd like to work with this, check the archives for
similar patches.  Most recent in a thread from Alex Nyberg starting
here:

http://marc.theaimsgroup.com/?l=linux-kernel&m=111062795600730&w=2

thanks,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

  parent reply	other threads:[~2005-06-08 20:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-08 20:27 [PATCH] capabilities not inherited Manfred Georg
2005-06-08 20:41 ` Alexander Nyberg
2005-06-08 21:26   ` Manfred Georg
2005-06-08 20:44 ` Chris Wright [this message]
2005-06-08 21:20   ` Alexander Nyberg
2005-06-08 21:33     ` Manfred Georg
2005-06-08 21:46       ` Alexander Nyberg
2005-06-08 21:54       ` Chris Wright
2005-06-08 21:59     ` Chris Wright
2005-06-08 23:49       ` Lee Revell
2005-06-09  2:59     ` David Wagner
2005-06-09 10:32       ` Alexander Nyberg
2005-06-09 14:55         ` David Wagner
2005-06-09 15:31           ` Lee Revell

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=20050608204430.GC9153@shell0.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgeorg@arl.wustl.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.