From: Mike Kazantsev <mk.fraggod@gmail.com>
To: linux-fsdevel@vger.kernel.org
Cc: "Serge E. Hallyn" <serue@us.ibm.com>
Subject: Re: POSIX CAP_DAC_READ_SEARCH doesn't bypass file read permissions?
Date: Tue, 29 Dec 2009 16:53:02 +0500 [thread overview]
Message-ID: <20091229165302.10f80f45@malediction> (raw)
In-Reply-To: <20091229052050.GA23226@us.ibm.com>
On Mon, 28 Dec 2009 23:20:50 -0600
"Serge E. Hallyn" <serue@us.ibm.com> wrote:
> Quoting Serge E. Hallyn (serue@us.ibm.com):
> > Quoting Mike Kazantsev (mk.fraggod@gmail.com):
> > > CAP_DAC_READ_SEARCH seem to be well-suited and sufficient for the
> > > task, according to docs:
> > >
> > > Bypass file read permission checks and directory read and
> > > execute permission checks.
> > >
> > >
> > > I can see it bypassing directory checks, but it fails to bypass
> > > file permission check.
>
> Egads, I'm sorry, Mike. I was sure that if there was any problem it
> would be in the exec_permission_lite path, that I had only checked DAC
> perms on the path. In fact, it's the DAC perms on the actual file
> which are the problem. I can reproduce your problem, and the
> following patch fixes it. Please confirm.
>
Indeed it works for both 2.6.32.2 and 2.6.33-rc2, thank you.
--
Mike Kazantsev // fraggod.net
prev parent reply other threads:[~2009-12-29 11:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-26 18:30 POSIX CAP_DAC_READ_SEARCH doesn't bypass file read permissions? Mike Kazantsev
2009-12-27 22:06 ` Serge E. Hallyn
2009-12-28 5:40 ` Mike Kazantsev
2009-12-28 7:03 ` Mike Kazantsev
2009-12-28 16:22 ` Serge E. Hallyn
2009-12-28 23:59 ` Mike Kazantsev
2009-12-29 5:20 ` Serge E. Hallyn
2009-12-29 11:53 ` Mike Kazantsev [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=20091229165302.10f80f45@malediction \
--to=mk.fraggod@gmail.com \
--cc=linux-fsdevel@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.