From mboxrd@z Thu Jan 1 00:00:00 1970 Reply-To: kernel-hardening@lists.openwall.com Message-ID: <4DFF5CCA.6070206@redhat.com> Date: Mon, 20 Jun 2011 10:44:26 -0400 From: Eric Paris MIME-Version: 1.0 References: <20110617171152.GA1389@albatros> <4DFF5795.9080609@redhat.com> <20110620144328.GA11933@albatros> In-Reply-To: <20110620144328.GA11933@albatros> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [kernel-hardening] Re: [RFC v2] security: intoduce ptrace_task_may_access_current To: Vasiliy Kulikov Cc: linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org, apparmor@lists.ubuntu.com, "selinux@tycho.nsa.gov Stephen Smalley" , James Morris , Eric Paris , John Johansen , kernel-hardening@lists.openwall.com, serge@hallyn.com List-ID: On 06/20/2011 10:43 AM, Vasiliy Kulikov wrote: > On Mon, Jun 20, 2011 at 10:22 -0400, Eric Paris wrote: >> serge even if you disagree with all of that, you are definitely >> going to need to review the capability changes added here. >> Personally I'd like to see all of the capability changes done as a >> separate patch from the ptrace changes. > I'm afraid the patch series will not be bisectable (capabilities and > ptrace code are very interconnected), but I'll try. Just add the new functions, describe them, document them, but don't use them. Then use them in the second patch. -Eric