From: Kentaro Takeda <takedakn@nttdata.co.jp>
To: Valdis.Kletnieks@vt.edu
Cc: Casey Schaufler <casey@schaufler-ca.com>,
"Serge E. Hallyn" <serue@us.ibm.com>,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, haradats@nttdata.co.jp,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
Al Viro <viro@ZenIV.linux.org.uk>
Subject: Re: [TOMOYO #9 (2.6.27-rc7-mm1) 1/6] LSM adapter functions.
Date: Wed, 01 Oct 2008 17:23:51 +0900 [thread overview]
Message-ID: <48E33397.1030709@nttdata.co.jp> (raw)
In-Reply-To: <62704.1222837526@turing-police.cc.vt.edu>
Valdis.Kletnieks@vt.edu wrote:
> On Tue, 30 Sep 2008 19:33:32 PDT, Casey Schaufler said:
>> I have always believed that MAC should come first, then DAC, because
>> MAC may care if you can see the mode bits. The current DAC before MAC
>> is an artifact of the desire for the LSM to behave cleanly as a
>> strictly additional mechanism. From an ideal security perspective
>> MAC should be first, but the pragmatic DAC first isn't going to cause
>> too much grief. If Tomoyo wants to do what I think is the right thing,
>> well, it's OK with me.
> I'm OK with the MAC going first as well
Current implementation is as follows.
- security_path_*: MAC before DAC
- security_inode_*: DAC before MAC
I can understand Casey and Valdis' MAC first approach from the ideal
security perspective. However, from the pragmatic perspective, we
prefer DAC before MAC approach as SELinux does. This approach doesn't
change error code returned to callers if requested access is denied
by DAC.
Regards,
next prev parent reply other threads:[~2008-10-01 8:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 9:03 [TOMOYO #9 (2.6.27-rc7-mm1) 0/6] TOMOYO Linux Kentaro Takeda
2008-09-24 9:03 ` [TOMOYO #9 (2.6.27-rc7-mm1) 1/6] LSM adapter functions Kentaro Takeda
2008-09-25 16:59 ` Serge E. Hallyn
2008-09-26 5:38 ` Kentaro Takeda
2008-09-26 13:04 ` Serge E. Hallyn
2008-09-29 4:04 ` Kentaro Takeda
2008-09-30 15:45 ` Serge E. Hallyn
2008-09-30 16:14 ` Stephen Smalley
2008-09-30 16:23 ` Serge E. Hallyn
2008-10-01 8:19 ` Kentaro Takeda
2008-10-01 2:33 ` Casey Schaufler
2008-10-01 5:05 ` Valdis.Kletnieks
2008-10-01 8:23 ` Kentaro Takeda [this message]
2008-10-01 21:15 ` Serge E. Hallyn
2008-10-02 5:04 ` Kentaro Takeda
2008-10-02 13:39 ` Serge E. Hallyn
2008-10-03 6:37 ` Kentaro Takeda
2008-10-03 13:09 ` Serge E. Hallyn
2008-10-06 2:19 ` Kentaro Takeda
2008-10-06 16:54 ` Serge E. Hallyn
2008-10-07 6:28 ` Kentaro Takeda
2008-09-24 9:03 ` [TOMOYO #9 (2.6.27-rc7-mm1) 2/6] Memory and pathname management functions Kentaro Takeda
2008-09-24 9:03 ` [TOMOYO #9 (2.6.27-rc7-mm1) 3/6] Common functions for TOMOYO Linux Kentaro Takeda
2008-09-24 9:03 ` [TOMOYO #9 (2.6.27-rc7-mm1) 4/6] Domain transition handler Kentaro Takeda
2008-09-24 9:03 ` [TOMOYO #9 (2.6.27-rc7-mm1) 5/6] File operation restriction part Kentaro Takeda
2008-09-24 9:03 ` [TOMOYO #9 (2.6.27-rc7-mm1) 6/6] Kconfig and Makefile Kentaro Takeda
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=48E33397.1030709@nttdata.co.jp \
--to=takedakn@nttdata.co.jp \
--cc=Valdis.Kletnieks@vt.edu \
--cc=casey@schaufler-ca.com \
--cc=haradats@nttdata.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=serue@us.ibm.com \
--cc=viro@ZenIV.linux.org.uk \
/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