From: Andrew Morgan <morgan@kernel.org>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: Linux Containers <containers@lists.osdl.org>,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH 2/2] capabilities: introduce per-process capability bounding set (v7)
Date: Fri, 16 Nov 2007 20:22:42 -0800 [thread overview]
Message-ID: <473E6C92.3040302@kernel.org> (raw)
In-Reply-To: <20071117034226.GA25867@sergelap.austin.ibm.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Serge E. Hallyn wrote:
>> I also think we should use CAP_SETPCAP for the privilege of manipulating
>> the bounding set. In many ways irrevocably removing a permission
>> requires the same level of due care as adding one (to pI).
>
> Aside from being heavy-handed, it also means that we are restricting the
> use of per-process capability bounding sets to kernels with file
> capabilities compiled in, right? Are we ok with that?
>
I am. :-)
Cheers
Andrew
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
iD8DBQFHPmyQQheEq9QabfIRAnnbAJ0c22LPNc1EnjWyvR4ZrwcyAiJDrgCeOdTj
TJFJwUK7UMkeX5M9ULzbN44=
=LMQP
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-11-17 4:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 23:16 [RFC PATCH 1/2] capabilities: define CONFIG_COMMONCAP Serge E. Hallyn
2007-11-15 23:17 ` [PATCH 2/2] capabilities: introduce per-process capability bounding set (v7) Serge E. Hallyn
2007-11-16 17:18 ` Andrew Morgan
[not found] ` <473DD0CB.7090403-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2007-11-17 3:42 ` Serge E. Hallyn
2007-11-17 4:22 ` Andrew Morgan [this message]
2007-11-15 23:23 ` [PATCH RFC] cgroups: implement device whitelist cgroup+lsm Serge E. Hallyn
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=473E6C92.3040302@kernel.org \
--to=morgan@kernel.org \
--cc=containers@lists.osdl.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serue@us.ibm.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