From: Russell Coker <russell@coker.com.au>
To: Joshua Brindle <jbrindle@tresys.com>
Cc: Stephen Smalley <sds@epoch.ncsc.mil>,
selinux@tycho.nsa.gov,
"Christopher J. PeBenito" <cpebenito@tresys.com>
Subject: Re: [RFC][PATCH] Control ability to have a writable executable mapping
Date: Mon, 15 Nov 2004 22:52:00 +1100 [thread overview]
Message-ID: <200411152252.07081.russell@coker.com.au> (raw)
In-Reply-To: <41914F8B.3060102@tresys.com>
On Wednesday 10 November 2004 10:15, Joshua Brindle <jbrindle@tresys.com>
wrote:
> I can't think of any circumstances where the domain which an application
> is in should have an impact on it's PaX flags.
Maybe instances of the application running in different domains will be
permitted to load different DSOs such that one domain is permitted to load a
DSO which wants write-execute access while another domain is not permitted to
load such DSOs.
It's just a hypothetical, I don't know of an example of this happening.
--
http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/ My home page
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
prev parent reply other threads:[~2004-11-15 11:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 18:40 [RFC][PATCH] Control ability to have a writable executable mapping Stephen Smalley
2004-11-09 21:05 ` Stephen Smalley
2004-11-10 15:35 ` Stephen Smalley
2004-12-01 17:02 ` Stephen Smalley
2004-11-09 23:15 ` Joshua Brindle
2004-11-10 15:25 ` Stephen Smalley
2004-11-15 11:52 ` Russell Coker [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=200411152252.07081.russell@coker.com.au \
--to=russell@coker.com.au \
--cc=cpebenito@tresys.com \
--cc=jbrindle@tresys.com \
--cc=sds@epoch.ncsc.mil \
--cc=selinux@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 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.