From: Andreas Gruenbacher <agruen@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: Christoph Hellwig <hch@infradead.org>,
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 20:17:03 +0100 [thread overview]
Message-ID: <200302152017.03259.agruen@suse.de> (raw)
In-Reply-To: <20030215183959.B22045@infradead.org>
On Saturday 15 February 2003 19:39, Christoph Hellwig wrote:
> On Sat, Feb 15, 2003 at 06:59:11PM +0100, Andreas Gruenbacher wrote:
> > > Please don't do the ugly flags stuff. We have fsuids and fsgids
> > > for exactly that reason (and because we're still lacking a
> > > credentials cache..).
> >
> > The XATTR_KERNEL_CONTEXT flag cannot be substituted by a uid/gid
> > change; it is unrelated to that; that's the whole point of it. It
> > would be possible to raise some other flag (such as a capability,
> > etc.) instead of passing an explicit flag, but that seems uglier
> > and more problematic/error prone to me.
>
> Then raise CAP_DAC_OVERRIDE. The right thing would be to pass down a
> struct cred, so we could pass down the magic sys_cred that allows all
> access (look at the XFS ACL code for details on that..), but
> unfortuantately we still don't have proper credentials although there
> were numerous patches around in the last years and we really want it
> for other reasons.
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?
> Magic flags that change the DAC checks work are ugly and will most
> certainly lead to bugs in some implementations sooner or later.
Maybe.
Thanks,
Andreas.
next prev parent reply other threads:[~2003-02-15 19:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-11 19:18 [PATCH] Extended attribute fixes, etc 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 [this message]
2003-02-15 21:09 ` Christoph Hellwig
2003-02-15 21:39 ` Andreas Gruenbacher
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=200302152017.03259.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