RE: [RFC v3 0/2] WhiteEgret LSM module
> Do you have a target date for posting that? Yes, we have the target date. We will submit WhiteEgret v4 by September. > 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? We will provide WEUA sample to be able to control a script program with WhiteEgret v4. Our WEUA sample does not identify whether to read or to read with the intent to execute. The sample has some restrictions. We consider that the restrictions can be resolved by implementing additional functions for WEUA. It is an implementation-dependent matter. Howerver, we are sure that the restrictions are acceptable for many applications. We would like to discuss about them with WhiteEgret v4 patch! -Original Message- > 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
RE: [RFC v3 0/2] WhiteEgret LSM module
> Do you have a target date for posting that? Yes, we have the target date. We will submit WhiteEgret v4 by September. > 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? We will provide WEUA sample to be able to control a script program with WhiteEgret v4. Our WEUA sample does not identify whether to read or to read with the intent to execute. The sample has some restrictions. We consider that the restrictions can be resolved by implementing additional functions for WEUA. It is an implementation-dependent matter. Howerver, we are sure that the restrictions are acceptable for many applications. We would like to discuss about them with WhiteEgret v4 patch! -Original Message- > 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
Re: [RFC v3 0/2] WhiteEgret LSM module
Quoting shinya1.tak...@toshiba.co.jp (shinya1.tak...@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
Re: [RFC v3 0/2] WhiteEgret LSM module
Quoting shinya1.tak...@toshiba.co.jp (shinya1.tak...@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
RE: [RFC v3 0/2] WhiteEgret LSM module
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. 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. 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. -Original Message- From: owner-linux-security-mod...@vger.kernel.org [mailto:owner-linux-security-mod...@vger.kernel.org] On Behalf Of Serge E. Hallyn Sent: Monday, April 2, 2018 5:08 AM To: koike masanobu(小池 正修 ＴＤＳＬ （ＩＳＥＣ）［ＳＥＣ運］) <masanobu2.ko...@toshiba.co.jp> Cc: jmor...@namei.org; se...@hallyn.com; linux-security-mod...@vger.kernel.org; linux-kernel@vger.kernel.org Subject: Re: [RFC v3 0/2] WhiteEgret LSM module Quoting Masanobu Koike (masanobu2.ko...@toshiba.co.jp): ... > Assumptions and ToDos > > 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 > root privilege. > - WEUA is reliable. > - It is allowed for scripting languages, e.g., Perl or Python, to read > 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-module" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [RFC v3 0/2] WhiteEgret LSM module
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. 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. 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. -Original Message- From: owner-linux-security-mod...@vger.kernel.org [mailto:owner-linux-security-mod...@vger.kernel.org] On Behalf Of Serge E. Hallyn Sent: Monday, April 2, 2018 5:08 AM To: koike masanobu(小池 正修 ＴＤＳＬ （ＩＳＥＣ）［ＳＥＣ運］) Cc: jmor...@namei.org; se...@hallyn.com; linux-security-mod...@vger.kernel.org; linux-kernel@vger.kernel.org Subject: Re: [RFC v3 0/2] WhiteEgret LSM module Quoting Masanobu Koike (masanobu2.ko...@toshiba.co.jp): ... > Assumptions and ToDos > > 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 > root privilege. > - WEUA is reliable. > - It is allowed for scripting languages, e.g., Perl or Python, to read > 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-module" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [RFC v3 0/2] WhiteEgret LSM module
Quoting Masanobu Koike (masanobu2.ko...@toshiba.co.jp): ... > Assumptions and ToDos > > 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 root privilege. > - WEUA is reliable. > - It is allowed for scripting languages, e.g., Perl or Python, > to read arbitrary scripts and to execute them. Hi, regardling the last one, do you have a plan for handling it?
Re: [RFC v3 0/2] WhiteEgret LSM module
Quoting Masanobu Koike (masanobu2.ko...@toshiba.co.jp): ... > Assumptions and ToDos > > 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 root privilege. > - WEUA is reliable. > - It is allowed for scripting languages, e.g., Perl or Python, > to read arbitrary scripts and to execute them. Hi, regardling the last one, do you have a plan for handling it?
