linux-kernel - Re: [RFC][PATCH 1/6] mprotect patch for use by SLIM

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: <1152898948.314.7.camel@localhost.localdomain>
Date:	Fri, 14 Jul 2006 10:42:28 -0700
From:	Dave Hansen <haveblue@...ibm.com>
To:	Kylene Jo Hall <kjhall@...ibm.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	LSM ML <linux-security-module@...r.kernel.org>,
	Dave Safford <safford@...ibm.com>,
	Mimi Zohar <zohar@...ibm.com>, Serge Hallyn <sergeh@...ibm.com>
Subject: Re: [RFC][PATCH 1/6] mprotect patch for use by SLIM

On Fri, 2006-07-14 at 10:24 -0700, Kylene Jo Hall wrote:
> This small patch makes mprotect available for use by SLIM for
> write revocation. 

Hmmm.   Do you really want mprotect() itself?  Or, do you just want to
keep people from writing?  (there is a difference :)

If somebody mmap()s something with write permissions, I would expect
them to expect to see rw in /proc/<pid>/maps.  If you use mprotect() on
that mmap() to remove the write permissions, the permissions will be
reflected in /proc/<pid>/maps.  

-- Dave

-
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/