From: David Howells <dhowells@redhat.com>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: dhowells@redhat.com,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
sds@tycho.nsa.gov, spotter@cs.columbia.edu,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add in_execve flag into task_struct.
Date: Thu, 05 Feb 2009 13:40:35 +0000 [thread overview]
Message-ID: <2690.1233841235@redhat.com> (raw)
In-Reply-To: <20090107190652.GA20311@us.ibm.com>
Serge E. Hallyn <serue@us.ibm.com> wrote:
> It's ugly, you can't get me to say it isn't ugly :), and it sets a scary
> bad precedent. But if David insists (in a reply to this msg) that this
> flag really is tops, then just ignore me. Anyway my point wasn't to
> block the patch but to raise discussion (so someone else could decide to
> block it :) on both the flag and security implications of these
> semantics.
I think it's probably the best way to support Tomoyo's security model without
reworking a chunk of execve().
David
next prev parent reply other threads:[~2009-02-05 13:41 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
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 [this message]
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=2690.1233841235@redhat.com \
--to=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=sds@tycho.nsa.gov \
--cc=serue@us.ibm.com \
--cc=spotter@cs.columbia.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 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.