From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add in_execve flag into task_struct.
Date: Tue, 6 Jan 2009 09:58:29 -0600 [thread overview]
Message-ID: <20090106155829.GA9773@us.ibm.com> (raw)
In-Reply-To: <200901060514.n065E462074929@www262.sakura.ne.jp>
Quoting Tetsuo Handa (penguin-kernel@i-love.sakura.ne.jp):
> Serge,
>
> James is now reviewing TOMOYO Linux patch and he is caring about
> your comment below.
>
> Serge E. Hallyn wrote:
> > I don't like the 'in_exec' bit in the task_struct, but adding LSM hooks
> > to let just TOMOYO mark whether you're in exec seems even uglier.
>
> Let me (once again) ask your comment on 'in_exec' approach
> originally suggested by David Howells ( http://lkml.org/lkml/2008/10/2/127 ).
I still don't like it. Now I gather the reason for this is that you
want to allow a less trusted domain to execute a file (in a new domain)
without giving it the right to read it? I'd be interested in hearing
whether others think that's a worthy goal.
-serge
next prev parent reply other threads:[~2009-01-06 16:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 5:14 [PATCH] Add in_execve flag into task_struct Tetsuo Handa
2009-01-06 15:58 ` Serge E. Hallyn [this message]
2009-01-06 17:09 ` Shaya Potter
2009-01-06 18:45 ` Stephen Smalley
2009-01-07 6:34 ` Tetsuo Handa
2009-01-07 19:06 ` Serge E. Hallyn
2009-01-08 6:17 ` Tetsuo Handa
2009-02-05 13:40 ` David Howells
2009-02-12 4:08 ` James Morris
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=20090106155829.GA9773@us.ibm.com \
--to=serue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
/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