From: Markku Savela <msa@moth.iki.fi>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] file capabilities: add no_file_caps switch (v2)
Date: Tue, 23 Sep 2008 10:21:54 +0300 [thread overview]
Message-ID: <87tzc7fht9.fsf@burp.tkv.asdf.org> (raw)
In-Reply-To: <bf035-3Tp-5@gated-at.bofh.it> (Andreas Gruenbacher's message of "Mon\, 22 Sep 2008 22\:20\:08 +0200")
Andreas Gruenbacher <agruen@suse.de> writes:
> Sure, that would work as well, except that I think that file
> capabilities should always default to "on" as they will become a
> standard security mechanism before long. We just don't have much
> system management tool support yet, and I would like to give that
> some more time safely, without putting users at unnecessary risk.
As I've said elsewhere, I consider above a bad move. The "file
capabilities" are just setgid/setuid executables in disguise (although
with little finer control).
I would prefer two choices for capabilities:
1) file capabilities, for those who think they work
2) no file capabilities, but just normal inheritance. There should be
nothing mystical about this. The credential (uid, groups) inherit
just fine without problems. Why not capabilities?
next parent reply other threads:[~2008-09-23 7:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2008-08-28 19:54 Serge Hallyn
2008-08-29 0:35 ` Andrew G. Morgan
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=87tzc7fht9.fsf@burp.tkv.asdf.org \
--to=msa@moth.iki.fi \
--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