From: "Andrew G. Morgan" <morgan@kernel.org>
To: Serge Hallyn <serue@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, dhowells@redhat.com, agruen@suse.de
Subject: Re: [PATCH 1/2] file capabilities: add no_file_caps switch (v2)
Date: Thu, 28 Aug 2008 17:35:04 -0700 [thread overview]
Message-ID: <48B74438.8070407@kernel.org> (raw)
In-Reply-To: <f79cd5c96d2996b984fdfe1c7d8300975f55e8e6.1219951973.git.serue@us.ibm.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Acked-by: Andrew G. Morgan <morgan@kernel.org>
Cheers
Andrew
Serge Hallyn wrote:
| Add a no_file_caps boot option when file capabilities are
| compiled into the kernel (CONFIG_SECURITY_FILE_CAPABILITIES=y).
|
| This allows distributions to ship a kernel with file capabilities
| compiled in, without forcing users to use (and understand and
| trust) them.
|
| When no_file_caps is specified at boot, then when a process executes
| a file, any file capabilities stored with that file will not be
| used in the calculation of the process' new capability sets.
|
| This means that booting with the no_file_caps boot option will
| not be the same as booting a kernel with file capabilities
| compiled out - in particular a task with CAP_SETPCAP will not
| have any chance of passing capabilities to another task (which
| isn't "really" possible anyway, and which may soon by killed
| altogether by David Howells in any case), and it will instead
| be able to put new capabilities in its pI. However since fI
| will always be empty and pI is masked with fI, it gains the
| task nothing.
|
| We also support the extra prctl options, setting securebits and
| dropping capabilities from the per-process bounding set.
|
| The other remaining difference is that killpriv, task_setscheduler,
| setioprio, and setnice will continue to be hooked. That will
| be noticable in the case where a root task changed its uid
| while keeping some caps, and another task owned by the new uid
| tries to change settings for the more privileged task.
|
| Signed-off-by: Serge Hallyn <serue@us.ibm.com>
| ---
| include/linux/capability.h | 4 ++++
| kernel/capability.c | 11 +++++++++++
| security/commoncap.c | 9 +++++++++
| 3 files changed, 24 insertions(+), 0 deletions(-)
|
| diff --git a/include/linux/capability.h b/include/linux/capability.h
| index 9d1fe30..c96c455 100644
| --- a/include/linux/capability.h
| +++ b/include/linux/capability.h
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFIt0Qi+bHCR3gb8jsRApyoAKC4brJOkrqsna3iDQ8xMFEPlyAW/wCbBHy+
xUaMSRInmcgNkYdoNJkxzOQ=
=zTib
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-08-29 0:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 19:54 [PATCH 1/2] file capabilities: add no_file_caps switch (v2) Serge Hallyn
2008-08-28 19:54 ` [PATCH 2/2] file capabilities: turn on by default Serge Hallyn
2008-08-29 0:37 ` Andrew G. Morgan
2008-08-29 0:35 ` Andrew G. Morgan [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-22 18:48 [PATCH 1/2] file capabilities: add no_file_caps switch (v2) Serge E. Hallyn
2008-09-22 19:16 ` Stephen Smalley
2008-09-22 20:09 ` Andreas Gruenbacher
2008-09-22 21:50 ` Serge E. Hallyn
2008-09-22 22:08 ` Andreas Gruenbacher
2008-09-23 6:48 ` James Morris
2008-09-22 22:57 ` Chris Wright
2008-09-23 15:51 ` Serge E. Hallyn
[not found] <beYE7-1Xc-41@gated-at.bofh.it>
[not found] ` <beZ72-2GM-5@gated-at.bofh.it>
[not found] ` <bf035-3Tp-5@gated-at.bofh.it>
2008-09-23 7:21 ` Markku Savela
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=48B74438.8070407@kernel.org \
--to=morgan@kernel.org \
--cc=agruen@suse.de \
--cc=dhowells@redhat.com \
--cc=linux-kernel@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 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.