From: Andreas Gruenbacher <agruen@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: Andrew Morton <akpm@digeo.com>,
linux-kernel@vger.kernel.org, "Theodore T'so" <tytso@mit.edu>
Subject: Re: [PATCH] Extended attribute fixes, etc.
Date: Sat, 15 Feb 2003 22:39:24 +0100 [thread overview]
Message-ID: <200302152239.24346.agruen@suse.de> (raw)
In-Reply-To: <20030215210922.A24685@infradead.org>
On Saturday 15 February 2003 22:09, Christoph Hellwig wrote:
> On Sat, Feb 15, 2003 at 08:17:03PM +0100, Andreas Gruenbacher wrote:
> > That sounds quite reasonable. I would have to raise CAP_SYS_ADMIN
> > for trusted EA's, though. Do you see any potential side effects
> > while a pretty powerful capability like CAP_SYS_ADMIN is
> > temporarily raised?
>
> Okay, something I missed when looking over your patches, otherwise
> I'd have shutde earlier :) Do you really think you want
> CAP_SYS_ADMIN for trusted EAs? Soon we'll get CAP_SYS_ADMIN as
> catchall like old suser()..
>
> Let me check what XFS uses for that purpose as soon as I'm back in
> the office.
The intention of Trusted Extended Attributes is for processes that
perform tasks that are relevant for the proper functioning of the
system, to allow them to use EAs. Other, non-privileged processes shall
have no access whatsoever to those EAs. This level of protection would
otherwise only be possible by providing a kernel module.
I would be quite happy with a new CAP_TRUSTED_PROCESS or whatever, but
going that route for all sorts of applications then we might soon end
up with an large number of capabilities. Maybe I'm wrong on that,
though.
Cheers,
Andreas.
prev parent reply other threads:[~2003-02-15 21:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-11 19:18 Andreas Gruenbacher
2003-02-11 20:32 ` Andrew Morton
2003-02-12 11:03 ` Andreas Gruenbacher
2003-02-15 11:07 ` Christoph Hellwig
2003-02-15 17:59 ` Andreas Gruenbacher
2003-02-15 18:39 ` Christoph Hellwig
2003-02-15 19:17 ` Andreas Gruenbacher
2003-02-15 21:09 ` Christoph Hellwig
2003-02-15 21:39 ` Andreas Gruenbacher [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=200302152239.24346.agruen@suse.de \
--to=agruen@suse.de \
--cc=akpm@digeo.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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
all inboxes | Powered by JetHome®