public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Chris Wright <chrisw@sous-sol.org>,
	casey@schaufler-ca.com,
	lsm <linux-security-module@vger.kernel.org>,
	James Morris <jmorris@namei.org>,
	Eric Paris <eparis@parisplace.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] security:  split ptrace checking in proc
Date: Wed, 14 May 2008 09:58:42 -0700	[thread overview]
Message-ID: <20080514165842.GD17453@sequoia.sous-sol.org> (raw)
In-Reply-To: <1210780216.28282.4.camel@moss-spartans.epoch.ncsc.mil>

* Stephen Smalley (sds@tycho.nsa.gov) wrote:
> What do you mean by "generic" in the above?  Just the fact that there
> wouldn't be any distinction between such access and access to a
> descriptor received explicitly via local IPC from the target task?

Basically, yeah.

> Ok, so perhaps the only distinction that makes sense is read vs.
> write/control, with all checks within proc except mem_write using the
> former and ptrace_attach and mem_write using the latter?

Yeah, that's what I was wondering, because maps seems to fall into the
readstate category as much as fd/ does (probably fdinfo/ is closer to
maps).

thanks,
-chris

      reply	other threads:[~2008-05-14 17:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-12 12:39 [RFC][PATCH] security: split ptrace checking in proc Stephen Smalley
2008-05-12 14:06 ` Casey Schaufler
2008-05-12 15:16   ` Stephen Smalley
2008-05-13 14:01   ` Stephen Smalley
2008-05-14  9:15     ` Chris Wright
2008-05-14 11:03       ` Stephen Smalley
2008-05-14 15:28         ` Chris Wright
2008-05-14 15:50           ` Stephen Smalley
2008-05-14 16:58             ` Chris Wright [this message]

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=20080514165842.GD17453@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=casey@schaufler-ca.com \
    --cc=eparis@parisplace.org \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=sds@tycho.nsa.gov \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox