Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   <shinya1.takumi@toshiba.co.jp>
To:     <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
Thread-Topic: [RFC v3 0/2] WhiteEgret LSM module
Thread-Index: AQHTyAJOnQ+9r2edhk+NYvbIB0nAd6PsWl+AgAVlmJA=
Date:   Thu, 5 Apr 2018 06:40:36 +0000
Message-ID: <OSBPR01MB21847D1D8A8BC8458CBAD39592BB0@OSBPR01MB2184.jpnprd01.prod.outlook.com>
References: <20180330083031.2199-1-masanobu2.koike@toshiba.co.jp>
 <20180401200827.GA28101@mail.hallyn.com>
In-Reply-To: <20180401200827.GA28101@mail.hallyn.com>
Accept-Language: ja-JP, en-US
Content-Language: ja-JP
received-spf: None (protection.outlook.com: toshiba.co.jp does not designate
 permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: ceb3ecd5-cb50-4267-8d23-08d59ac02376
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Apr 2018 06:40:36.1694
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: f109924e-fb71-4ba0-b2cc-65dcdf6fbe4f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: OSBPR01MB1783
MSSCP.TransferMailToMossAgent: 103
X-OriginatorOrg: toshiba.co.jp
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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 ac=
cess control for script programs.

The latest WhiteEgret cannot control script programs since script files rea=
d 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.=20
We consider that the control can be realized using the read system call hoo=
king.

Now, we are developing WhiteEgret with the read system call hooking and WEU=
A which controls the script files to be read to interpreters using informat=
ion from the read system call hooking and white list.

-----Original Message-----
From: owner-linux-security-module@vger.kernel.org [mailto:owner-linux-secur=
ity-module@vger.kernel.org] On Behalf Of Serge E. Hallyn
Sent: Monday, April 2, 2018 5:08 AM
To: koike masanobu(=1B$B>.CS=1B(B =1B$B@5=3D$=1B(B =1B$B#T#D#S#L=1B(B =1B$B=
!J#I#S#E#C!K!N#S#E#C1?!O=1B(B) <masanobu2.koike@toshiba.co.jp>
Cc: jmorris@namei.org; serge@hallyn.com; linux-security-module@vger.kernel.=
org; linux-kernel@vger.kernel.org
Subject: Re: [RFC v3 0/2] WhiteEgret LSM module

Quoting Masanobu Koike (masanobu2.koike@toshiba.co.jp):
...
> Assumptions and ToDos
>=20
> At this stage, WhiteEgret assumes the following.
> Relaxing these assumptions are future works.
> - Root is not compromised. And using a whitelist and a WEUA requires=20
> root privilege.
> - WEUA is reliable.
> - It is allowed for scripting languages, e.g., Perl or Python, to read=20
> arbitrary scripts and to execute them.

Hi,

regardling the last one, do you have a plan for handling it?
--
To unsubscribe from this list: send the line "unsubscribe linux-security-mo=
dule" in the body of a message to majordomo@vger.kernel.org More majordomo =
info at  http://vger.kernel.org/majordomo-info.html