Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1646256 > unrolled thread

Re: [PATCH 0/8] CaitSith LSM module

Started byTetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
First post2017-05-21 07:10 +0200
Last post2017-05-21 08:00 +0200
Articles 3 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH 0/8] CaitSith LSM module Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp> - 2017-05-21 07:10 +0200
    Re: [PATCH 0/8] CaitSith LSM module John Johansen <john.johansen@canonical.com> - 2017-05-21 07:40 +0200
      Re: [PATCH 0/8] CaitSith LSM module Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp> - 2017-05-21 08:00 +0200

#1646256 — Re: [PATCH 0/8] CaitSith LSM module

FromTetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Date2017-05-21 07:10 +0200
SubjectRe: [PATCH 0/8] CaitSith LSM module
Message-ID<tJrhT-3bg-1@gated-at.bofh.it>
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?



On 5th March 2017, a CTF game was held in an event titled
"CyberColosseo x SecCon" ( http://2016.seccon.jp/news/#137 ). I gave a
simple troubleshooting-like system-analyzing quiz using SSH shell session
where operations are restricted by CaitSith.

Since the VM will be useful as an example of how to configure
CaitSith's policy configuration, I made a downloadable version.

  http://osdn.jp/frs/redir.php?m=jaist&f=/caitsith/67303/SecCon20170305-CaitSith.zip
  MD5: 99bad6936d8cdeb37d0d6af99265a2ac

This VM is configured for VMware Player 12 / 4 CPUs / 2048MB RAM.
An IPv4 address will be assigned upon boot using DHCP service on the host network.
SSH username and password are both "caitsith".

[toc] | [next] | [standalone]


#1646260

FromJohn Johansen <john.johansen@canonical.com>
Date2017-05-21 07:40 +0200
Message-ID<tJrKV-3Ec-5@gated-at.bofh.it>
In reply to#1646256
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)


> 
> 
> On 5th March 2017, a CTF game was held in an event titled
> "CyberColosseo x SecCon" ( http://2016.seccon.jp/news/#137 ). I gave a
> simple troubleshooting-like system-analyzing quiz using SSH shell session
> where operations are restricted by CaitSith.
> 
> Since the VM will be useful as an example of how to configure
> CaitSith's policy configuration, I made a downloadable version.
> 
>   http://osdn.jp/frs/redir.php?m=jaist&f=/caitsith/67303/SecCon20170305-CaitSith.zip
>   MD5: 99bad6936d8cdeb37d0d6af99265a2ac
> 
> This VM is configured for VMware Player 12 / 4 CPUs / 2048MB RAM.
> An IPv4 address will be assigned upon boot using DHCP service on the host network.
> SSH username and password are both "caitsith".
> 

[toc] | [prev] | [next] | [standalone]


#1646263

FromTetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Date2017-05-21 08:00 +0200
Message-ID<tJs4i-3Ly-3@gated-at.bofh.it>
In reply to#1646260
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.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web