From: "Serge E. Hallyn" <serge@hallyn.com>
To: shinya1.takumi@toshiba.co.jp
Cc: serge@hallyn.com, jmorris@namei.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC v3 0/2] WhiteEgret LSM module
Date: Sun, 8 Apr 2018 10:51:15 -0500 [thread overview]
Message-ID: <20180408155114.GE9715@mail.hallyn.com> (raw)
In-Reply-To: <OSBPR01MB21847D1D8A8BC8458CBAD39592BB0@OSBPR01MB2184.jpnprd01.prod.outlook.com>
Quoting shinya1.takumi@toshiba.co.jp (shinya1.takumi@toshiba.co.jp):
> I am one of developers of WhiteEgret.
>
> > regardling the last one, do you have a plan for handling it?
> Yes, we have a plan to release WhiteEgret v4 patch with a WEUA sample of access control for script programs.
Do you have a target date for posting that?
> The latest WhiteEgret cannot control script programs since script files read by an interpreter are not hooked by the execve system call.
> We consider that script programs can be controlled by controlling the files inputted by interpreters, accordingly.
> We consider that the control can be realized using the read system call hooking.
So you have a design for being able to differentiate the interpreters reading
versus reading with the intent to execute? With or without their help?
> Now, we are developing WhiteEgret with the read system call hooking and WEUA which controls the script files to be read to interpreters using information from the read system call hooking and white list.
-serge
next prev parent reply other threads:[~2018-04-08 15:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-30 8:30 [RFC v3 0/2] WhiteEgret LSM module Masanobu Koike
2018-04-01 20:08 ` Serge E. Hallyn
2018-04-05 6:40 ` shinya1.takumi
2018-04-08 15:51 ` Serge E. Hallyn [this message]
2018-04-13 4:30 ` shinya1.takumi
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=20180408155114.GE9715@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=shinya1.takumi@toshiba.co.jp \
/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).