From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: John Johansen <john.johansen@canonical.com>
Cc: linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/8] CaitSith LSM module
Date: Sat, 1 Sep 2018 22:04:54 +0900 [thread overview]
Message-ID: <b72491b3-834e-e073-0e40-a61d134725db@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <7cab86a5-e115-0905-4d72-8cae7f6540b9@schaufler-ca.com>
On 2017/10/22 2:17, Casey Schaufler wrote:
>> As one year elapsed since I proposed CaitSith for upstream, I'd like to
>> hear the status again. I looked at
>> http://schd.ws/hosted_files/lss2017/8b/201709-LinuxSecuritySummit-Stacking.pdf .
>> How is ETA for Security Module Stacking? Is it a half year or so?
>
> Assuming that I can keep working on stacking at my current level,
> and that we can work out a couple issues with audit and networking
> there is a possibility we're looking at mid 2018 for stacking. The
> increased interest in security module namespaces for containers is
> helping make stacking seem important to more people.
>
>> If it is likely take longer, should I resume proposing CaitSith for now
>> as one of "Minor modules" except security_module_enable() check added
>> until Security Module Stacking work completes? Or should I wait for
>> completion of stacking work? I want to know it, for recent proposals are
>> rather staying silent.
>
> I wouldn't wait if it was my project, but I have been known
> to be more aggressive than is good for me from time to time.
>
It seems that stacking needs some more time. Manual with updated patch for
current source code is available at https://caitsith.osdn.jp/index2.html .
John, if you can resume reviewing, I'd like to propose CaitSith as one of
"Minor modules" except security_module_enable() check.
Regards.
WARNING: multiple messages have this Message-ID (diff)
From: penguin-kernel@I-love.SAKURA.ne.jp (Tetsuo Handa)
To: linux-security-module@vger.kernel.org
Subject: [PATCH 0/8] CaitSith LSM module
Date: Sat, 1 Sep 2018 22:04:54 +0900 [thread overview]
Message-ID: <b72491b3-834e-e073-0e40-a61d134725db@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <7cab86a5-e115-0905-4d72-8cae7f6540b9@schaufler-ca.com>
On 2017/10/22 2:17, Casey Schaufler wrote:
>> As one year elapsed since I proposed CaitSith for upstream, I'd like to
>> hear the status again. I looked at
>> http://schd.ws/hosted_files/lss2017/8b/201709-LinuxSecuritySummit-Stacking.pdf .
>> How is ETA for Security Module Stacking? Is it a half year or so?
>
> Assuming that I can keep working on stacking at my current level,
> and that we can work out a couple issues with audit and networking
> there is a possibility we're looking at mid 2018 for stacking. The
> increased interest in security module namespaces for containers is
> helping make stacking seem important to more people.
>
>> If it is likely take longer, should I resume proposing CaitSith for now
>> as one of "Minor modules" except security_module_enable() check added
>> until Security Module Stacking work completes? Or should I wait for
>> completion of stacking work? I want to know it, for recent proposals are
>> rather staying silent.
>
> I wouldn't wait if it was my project, but I have been known
> to be more aggressive than is good for me from time to time.
>
It seems that stacking needs some more time. Manual with updated patch for
current source code is available at https://caitsith.osdn.jp/index2.html .
John, if you can resume reviewing, I'd like to propose CaitSith as one of
"Minor modules" except security_module_enable() check.
Regards.
next prev parent reply other threads:[~2018-09-01 13:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 12:49 [PATCH 0/8] CaitSith LSM module Tetsuo Handa
2016-10-21 12:49 ` [PATCH 1/8] CaitSith: Add header file Tetsuo Handa
2016-10-21 12:49 ` [PATCH 2/8] CaitSith: Add pathname calculation functions Tetsuo Handa
2016-10-21 12:49 ` [PATCH 3/8] CaitSith: Add policy I/O functions Tetsuo Handa
2016-10-21 12:49 ` [PATCH 4/8] CaitSith: Add permission check functions Tetsuo Handa
2016-10-21 12:49 ` [PATCH 5/8] CaitSith: Add LSM adapter functions Tetsuo Handa
2016-10-21 12:49 ` [PATCH 6/8] CaitSith: Add policy loader functions Tetsuo Handa
2016-10-21 12:49 ` [PATCH 7/8] CaitSith: Add garbage collector functions Tetsuo Handa
2016-10-21 12:49 ` [PATCH 8/8] CaitSith: Add Kconfig and Makefile Tetsuo Handa
2016-10-24 4:44 ` [PATCH 0/8] CaitSith LSM module James Morris
2016-10-24 14:39 ` John Johansen
2016-10-24 18:18 ` John Johansen
2016-10-25 11:26 ` Tetsuo Handa
2016-11-23 6:31 ` Tetsuo Handa
2016-11-23 18:51 ` John Johansen
2017-05-21 4:59 ` Tetsuo Handa
2017-05-21 4:59 ` Tetsuo Handa
2017-05-21 5:31 ` John Johansen
2017-05-21 5:31 ` John Johansen
2017-05-21 5:59 ` Tetsuo Handa
2017-05-21 5:59 ` Tetsuo Handa
2017-10-21 10:59 ` Tetsuo Handa
2017-10-21 10:59 ` Tetsuo Handa
2017-10-21 17:17 ` Casey Schaufler
2017-10-21 17:17 ` Casey Schaufler
2018-09-01 13:04 ` Tetsuo Handa [this message]
2018-09-01 13:04 ` Tetsuo Handa
2018-09-05 16:22 ` John Johansen
2018-09-05 16:22 ` John Johansen
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=b72491b3-834e-e073-0e40-a61d134725db@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=john.johansen@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
/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.