From: James Morris <jmorris@namei.org>
To: David Madore <david.madore@ens.fr>
Cc: Linux Kernel mailing-list <linux-kernel@vger.kernel.org>
Subject: Re: understanding Linux capabilities brokenness
Date: Tue, 9 Aug 2005 01:53:49 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.63.0508090152210.20505@excalibur.intercode> (raw)
In-Reply-To: <20050809045916.GA3157@clipper.ens.fr>
On Tue, 9 Aug 2005, David Madore wrote:
> the "process management" part. For example, I might like to run this
> or that binary, which claims it needs to be run as root, with a
> limited set of capabilities: the current Linux kernels make this quite
> impossible.
Not impossible with SELinux.
- James
--
James Morris
<jmorris@namei.org>
prev parent reply other threads:[~2005-08-09 5:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 21:12 understanding Linux capabilities brokenness David Madore
2005-08-08 22:32 ` David Madore
2005-08-08 23:53 ` David Wagner
2005-08-09 1:50 ` Theodore Ts'o
2005-08-09 4:46 ` James Morris
2005-08-09 8:09 ` Jan Engelhardt
2005-08-09 15:16 ` Christopher Warner
2005-08-09 20:20 ` Kyle Moffett
2005-08-09 4:59 ` David Madore
2005-08-09 5:53 ` James Morris [this message]
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=Pine.LNX.4.63.0508090152210.20505@excalibur.intercode \
--to=jmorris@namei.org \
--cc=david.madore@ens.fr \
--cc=linux-kernel@vger.kernel.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