From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: john.johansen@canonical.com, linux-security-module@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/8] CaitSith LSM module
Date: Sun, 21 May 2017 14:59:25 +0900 [thread overview]
Message-ID: <201705211459.EGB48959.OFVFOSHtFJMLQO@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <8c6da617-3325-d60d-805f-5e5c1fa322c6@canonical.com>
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.
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: Sun, 21 May 2017 14:59:25 +0900 [thread overview]
Message-ID: <201705211459.EGB48959.OFVFOSHtFJMLQO@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <8c6da617-3325-d60d-805f-5e5c1fa322c6@canonical.com>
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-05-21 5:59 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 [this message]
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
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=201705211459.EGB48959.OFVFOSHtFJMLQO@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.