From: John Johansen <john.johansen@canonical.com>
To: James Morris <jmorris@namei.org>
Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
linux-security-module@vger.kernel.org,
linux-fsdevel@vger.kernel.org, Al Viro <viro@ftp.linux.org.uk>
Subject: Re: [RFC] LSM/TOMOYO: LSM hooks for chmod/chown/chroot/mount/open/execve
Date: Thu, 08 Oct 2009 08:03:53 -0700 [thread overview]
Message-ID: <4ACDFF59.3080005@canonical.com> (raw)
In-Reply-To: <alpine.LRH.2.00.0910072212530.20127@tundra.namei.org>
James Morris wrote:
> On Sun, 6 Sep 2009, Tetsuo Handa wrote:
>
>> Hello.
>>
>> I released TOMOYO 1.7.0 (non-LSM version of TOMOYO Linux).
>> http://sourceforge.jp/projects/tomoyo/lists/archive/users-en/2009-September/000092.html
>>
>> Before resuming TOMOYO 2.x (LSM version of TOMOYO Linux), I'd like to show you
>> what hooks I want to pick up from http://sourceforge.jp/projects/tomoyo/svn/view/trunk/1.7.x/ccs-patch/patches/ccs-patch-2.6.31.diff?view=markup&root=tomoyo .
>
> I'd be interested to know what other pathname folk think about these
> hooks. Are they useful for AppArmor?
>
The LSM hooks Tetsuo post http://lkml.org/lkml/2009/10/4/36 ,
http://lkml.org/lkml/2009/10/4/37 , http://lkml.org/lkml/2009/10/4/34 are all
very useful to AppArmor.
john
prev parent reply other threads:[~2009-10-08 15:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-06 5:28 [RFC] LSM/TOMOYO: LSM hooks for chmod/chown/chroot/mount/open/execve Tetsuo Handa
2009-09-16 11:50 ` [PATCH] LSM hooks for chmod/chown/chroot/mount Tetsuo Handa
2009-10-07 11:14 ` [RFC] LSM/TOMOYO: LSM hooks for chmod/chown/chroot/mount/open/execve James Morris
2009-10-08 15:03 ` John Johansen [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=4ACDFF59.3080005@canonical.com \
--to=john.johansen@canonical.com \
--cc=jmorris@namei.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=viro@ftp.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;
as well as URLs for NNTP newsgroup(s).