From: Ivan Gyurdiev <ivg2@cornell.edu>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: selinux@tycho.nsa.gov
Subject: Execmem boolean
Date: Sun, 26 Jun 2005 17:42:42 -0400 [thread overview]
Message-ID: <1119822163.4357.9.camel@localhost.localdomain> (raw)
Something needs to be done about the allow_execmem boolean -
the default strict policy configuration on Fedora disables it,
which causes X not to work out of the box under strict policy.
I think this is highly undesirable.
Should allow_execmem be enabled by default?
I know Stephen was asking about more fine-grained control
over allow_execmem and allow_execmod.
How can we combine those two requirements to come up with
a better solution?
Perhaps have allow_execmem turned on by default,
and then and-ed with per application booleans, we can
turn it off for selected applications?
The opposite approach (off by default, turn on
per application) doesn't work quite so well, beause
then you have per application booleans not respecting
the value of a global allow_execmem...
Or, we could get rid of allow_execmem completely, and
have only per application booleans...
--------
P.S. Please remove the gift port from types/network.te,
because otherwise the gift domain won't compile - this port is
restricted to gift.te.
--
Ivan Gyurdiev <ivg2@cornell.edu>
Cornell University
--
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.
next reply other threads:[~2005-06-26 21:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-26 21:42 Ivan Gyurdiev [this message]
2005-06-27 11:59 ` Execmem boolean Ivan Gyurdiev
2005-06-27 14:49 ` Stephen Smalley
2005-06-29 17:33 ` Daniel J Walsh
2005-06-29 18:49 ` Stephen Smalley
2005-06-29 18:54 ` Ivan Gyurdiev
2005-06-29 19:00 ` Stephen Smalley
2005-06-29 19:37 ` Daniel J Walsh
2005-06-29 19:58 ` Stephen Smalley
2005-06-29 20:07 ` Ivan Gyurdiev
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=1119822163.4357.9.camel@localhost.localdomain \
--to=ivg2@cornell.edu \
--cc=dwalsh@redhat.com \
--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.