mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Casey Schaufler <casey@schaufler-ca.com>
To: rgarcia@kotasoft.com, linux-kernel@vger.kernel.org
Subject: Re: Request change in behaviour of capability inheritance.
Date: Thu, 8 Mar 2007 08:24:38 -0800 (PST)	[thread overview]
Message-ID: <887.65866.qm@web36605.mail.mud.yahoo.com> (raw)
In-Reply-To: <15429.83.60.135.204.1173342736.squirrel@webmail2.digitalinet.com>


--- rgarcia@kotasoft.com wrote:

> I think that the current behaviour of capability
> inheritance across exec()
> is not optimal.
> 
> The current behaviour consists in all effective and
> permitted capabilities
> are cleared across a exec(). This is because it
> seems to be intended that
> in the future the executable files have a set of
> "allowed" and "forced"
> capabilities.

File based capabilities are the same
effective, permitted, and inheritable
sets that the process has. Unless the
thinking has shifted over the last couple
weeks (it happens from time to time)
the inheritable set is what you're
missing.



Casey Schaufler
casey@schaufler-ca.com

  reply	other threads:[~2007-03-08 16:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-08  8:32 rgarcia
2007-03-08 16:24 ` Casey Schaufler [this message]
2007-03-08 17:00   ` rgarcia

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=887.65866.qm@web36605.mail.mud.yahoo.com \
    --to=casey@schaufler-ca.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgarcia@kotasoft.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®