From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: casey@schaufler-ca.com
Cc: linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/8] CaitSith LSM module
Date: Sat, 21 Oct 2017 19:59:08 +0900 [thread overview]
Message-ID: <201710211959.CEC65165.SQJOLOFVOtFFHM@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <201705211459.EGB48959.OFVFOSHtFJMLQO@I-love.SAKURA.ne.jp>
Tetsuo Handa wrote:
> John Johansen wrote:
> > On 05/20/2017 09:59 PM, Tetsuo Handa wrote:
> > > John Johansen wrote:
> > >> On 11/22/2016 10:31 PM, Tetsuo Handa wrote:
> > >>> Tetsuo Handa wrote:
> > >>>> John Johansen wrote:
> > >>>>>> In order to minimize the burden of reviewing, this patchset implements
> > >>>>>> only functionality of checking program execution requests (i.e. execve()
> > >>>>>> system call) using pathnames. I'm planning to add other functionalities
> > >>>>>> after this version got included into mainline. You can find how future
> > >>>>>> versions of CaitSith will look like at http://caitsith.osdn.jp/ .
> > >>>>>>
> > >>>>> Thanks I've started working my way through this, but it is going to take
> > >>>>> me a while.
> > >>>>>
> > >>>>
> > >>>> Thank you for your time.
> > >>>
> > >>> May I hear the status? Is there something I can do other than waiting?
> > >>>
> > >> progressing very slowly, I have some time over the next few days as its a
> > >> long weekend here in the US some hopefully I can finish this up
> > >>
> > >
> > > May I hear the status again?
> > >
> > Yes, sorry. I just haven't had time too look at it recently. I am sorry that
> > it has been so long. I am just going to have to book a day off and do it. I'll
> > see if I can't get a day next week (getting late but I can try or the following)
>
> No problem. ;-) I assume reviewing a new module takes at least one year.
> Thank you for remembering.
>
I'm still fighting with OOM killer related problems at MM subsystem. ;-)
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?
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.
Regards.
next prev parent reply other threads:[~2017-10-21 10:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 12:49 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 5:31 ` John Johansen
2017-05-21 5:59 ` Tetsuo Handa
2017-10-21 10:59 ` Tetsuo Handa [this message]
2017-10-21 17:17 ` Casey Schaufler
2018-09-01 13:04 ` Tetsuo Handa
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=201710211959.CEC65165.SQJOLOFVOtFFHM@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=casey@schaufler-ca.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®