User: Password:
Subscribe / Log in / New account

Re: [PATCH] ptrace: allow restriction of ptrace scope

From:  James Morris <>
To:  Theodore Tso <>
Subject:  Re: [PATCH] ptrace: allow restriction of ptrace scope
Date:  Mon, 21 Jun 2010 10:52:11 +1000 (EST)
Cc:  Casey Schaufler <>, Alan Cox <>, Kees Cook <>, Randy Dunlap <>,, Andrew Morton <>, Jiri Kosina <>, Dave Young <>, Martin Schwidefsky <>, Roland McGrath <>, Oleg Nesterov <>, "H. Peter Anvin" <>, David Howells <>, Ingo Molnar <>, Peter Zijlstra <>, "Eric W. Biederman" <>,, Stephen Smalley <>, Daniel J Walsh <>,
Archive-link:  Article, Thread

On Fri, 18 Jun 2010, Theodore Tso wrote:

> Yet I would really like a number of features such as this ptrace scope idea ---
> which I think is a useful feature, and it may be that stacking is the only
> way we can resolve this debate.

We've already reached a consensus that these things should be put into a 
separate LSM so we can evaluate the possible need for some form of 
stacking or a security library API.

Note that people using SELinux or AppArmor already have the ability to 
restrict ptrace, and they would thus not need to stack this function if it 
were in a separate LSM.

Do you have a use-case where stacking would be useful here?

- James
James Morris
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to
More majordomo info at

(Log in to post comments)

Copyright © 2010, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds