From: Serge Hallyn <serge.hallyn@canonical.com>
To: Rob Landley <rob@landley.net>
Cc: Andy Lutomirski <luto@amacapital.net>,
James Morris <james.l.morris@oracle.com>,
linux-security-module@vger.kernel.org,
Casey Schaufler <casey@schaufler-ca.com>,
linux-kernel@vger.kernel.org, Eric Paris <eparis@redhat.com>,
"Andrew G. Morgan" <morgan@kernel.org>,
mtk.manpages@gmail.com
Subject: Re: [PATCH] Document how capability bits work
Date: Sun, 9 Dec 2012 23:57:53 -0600 [thread overview]
Message-ID: <20121210055753.GA3689@sergelap> (raw)
In-Reply-To: <1354960297.7646.0@driftwood>
Quoting Rob Landley (rob@landley.net):
> The fact that you need multiple sets of capabilities per process
> (permitted, inheritable, effective), plus MORE sets (plural) of
> capabilities attached to executable files, plus the "capability
> bounding set" which is presumably so selinux can mess with it, plus
The bounding set was in large part a workaround for the absence of the
user namespace (and, at the time, the devices cgroup).
(Now libcap-ng uses it to try and make capabilities generally easier to
use.)
-serge
next prev parent reply other threads:[~2012-12-10 5:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 18:20 [PATCH] Document how capability bits work Andy Lutomirski
2012-12-07 19:21 ` Serge Hallyn
2012-12-07 19:32 ` Andy Lutomirski
2012-12-08 1:10 ` Rob Landley
2012-12-08 1:27 ` Andy Lutomirski
2012-12-08 9:51 ` Rob Landley
2012-12-10 5:57 ` Serge Hallyn [this message]
2012-12-09 9:54 ` Michael Kerrisk (man-pages)
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=20121210055753.GA3689@sergelap \
--to=serge.hallyn@canonical.com \
--cc=casey@schaufler-ca.com \
--cc=eparis@redhat.com \
--cc=james.l.morris@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=morgan@kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=rob@landley.net \
/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