Hello Andy,
(Sorry for my late response)
On Thu, Apr 27, 2017 at 12:09 AM, Andy Lutomirski wrote:
> On Tue, Apr 25, 2017 at 5:23 AM, Djalal Harouni wrote:
>> If "limit_pids=1" mount option is set then do not instantiate pids that
>> we can not ptrace.
Hello Andy,
(Sorry for my late response)
On Thu, Apr 27, 2017 at 12:09 AM, Andy Lutomirski wrote:
> On Tue, Apr 25, 2017 at 5:23 AM, Djalal Harouni wrote:
>> If "limit_pids=1" mount option is set then do not instantiate pids that
>> we can not ptrace. "limit_pids=1" means that procfs should
On Tue, Apr 25, 2017 at 5:23 AM, Djalal Harouni wrote:
> If "limit_pids=1" mount option is set then do not instantiate pids that
> we can not ptrace. "limit_pids=1" means that procfs should only contain
> pids that the caller can ptrace.
>
> Cc: Kees Cook
On Tue, Apr 25, 2017 at 5:23 AM, Djalal Harouni wrote:
> If "limit_pids=1" mount option is set then do not instantiate pids that
> we can not ptrace. "limit_pids=1" means that procfs should only contain
> pids that the caller can ptrace.
>
> Cc: Kees Cook
> Cc: Andy Lutomirski
> Signed-off-by:
If "limit_pids=1" mount option is set then do not instantiate pids that
we can not ptrace. "limit_pids=1" means that procfs should only contain
pids that the caller can ptrace.
Cc: Kees Cook
Cc: Andy Lutomirski
Signed-off-by: Djalal Harouni
If "limit_pids=1" mount option is set then do not instantiate pids that
we can not ptrace. "limit_pids=1" means that procfs should only contain
pids that the caller can ptrace.
Cc: Kees Cook
Cc: Andy Lutomirski
Signed-off-by: Djalal Harouni
---
fs/proc/base.c | 9 +
1 file changed, 9
6 matches
Mail list logo