linux-kernel - Re: [RFC][PATCH] security: split ptrace checking in proc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20080514165842.GD17453@sequoia.sous-sol.org>
Date:	Wed, 14 May 2008 09:58:42 -0700
From:	Chris Wright <chrisw@...s-sol.org>
To:	Stephen Smalley <sds@...ho.nsa.gov>
Cc:	Chris Wright <chrisw@...s-sol.org>, casey@...aufler-ca.com,
	lsm <linux-security-module@...r.kernel.org>,
	James Morris <jmorris@...ei.org>,
	Eric Paris <eparis@...isplace.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [RFC][PATCH] security:  split ptrace checking in proc

* Stephen Smalley (sds@...ho.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/