From: Eric Paris <eparis@redhat.com>
To: Vasiliy Kulikov <segoon@openwall.com>
Cc: linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, apparmor@lists.ubuntu.com,
"selinux@tycho.nsa.gov Stephen Smalley" <sds@tycho.nsa.gov>,
James Morris <jmorris@namei.org>,
Eric Paris <eparis@parisplace.org>,
John Johansen <john.johansen@canonical.com>,
kernel-hardening@lists.openwall.com, serge@hallyn.com
Subject: [kernel-hardening] Re: [RFC v2] security: intoduce ptrace_task_may_access_current
Date: Mon, 20 Jun 2011 10:44:26 -0400 [thread overview]
Message-ID: <4DFF5CCA.6070206@redhat.com> (raw)
In-Reply-To: <20110620144328.GA11933@albatros>
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
WARNING: multiple messages have this Message-ID (diff)
From: Eric Paris <eparis@redhat.com>
To: Vasiliy Kulikov <segoon@openwall.com>
Cc: linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, apparmor@lists.ubuntu.com,
"selinux@tycho.nsa.gov Stephen Smalley" <sds@tycho.nsa.gov>,
James Morris <jmorris@namei.org>,
Eric Paris <eparis@parisplace.org>,
John Johansen <john.johansen@canonical.com>,
kernel-hardening@lists.openwall.com, serge@hallyn.com
Subject: Re: [RFC v2] security: intoduce ptrace_task_may_access_current
Date: Mon, 20 Jun 2011 10:44:26 -0400 [thread overview]
Message-ID: <4DFF5CCA.6070206@redhat.com> (raw)
In-Reply-To: <20110620144328.GA11933@albatros>
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
next prev parent reply other threads:[~2011-06-20 14:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 17:11 [kernel-hardening] [RFC v2] security: intoduce ptrace_task_may_access_current Vasiliy Kulikov
2011-06-17 17:11 ` Vasiliy Kulikov
2011-06-20 14:22 ` [kernel-hardening] " Eric Paris
2011-06-20 14:22 ` Eric Paris
2011-06-20 14:40 ` [kernel-hardening] " Vasiliy Kulikov
2011-06-20 14:40 ` Vasiliy Kulikov
2011-06-20 14:43 ` [kernel-hardening] " Vasiliy Kulikov
2011-06-20 14:43 ` Vasiliy Kulikov
2011-06-20 14:44 ` Eric Paris [this message]
2011-06-20 14:44 ` Eric Paris
2011-06-20 15:00 ` [kernel-hardening] " Serge Hallyn
2011-06-20 15:00 ` Serge Hallyn
2011-06-20 15:44 ` [kernel-hardening] " Vasiliy Kulikov
2011-06-20 15:44 ` Vasiliy Kulikov
2011-06-20 15:51 ` [kernel-hardening] " Serge E. Hallyn
2011-06-20 15:51 ` Serge E. Hallyn
2011-06-20 16:50 ` [kernel-hardening] " Eric Paris
2011-06-20 16:50 ` Eric Paris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DFF5CCA.6070206@redhat.com \
--to=eparis@redhat.com \
--cc=apparmor@lists.ubuntu.com \
--cc=eparis@parisplace.org \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=segoon@openwall.com \
--cc=serge@hallyn.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.