From: Daniel J Walsh <dwalsh@redhat.com>
To: ivg2@cornell.edu
Cc: Stephen Smalley <sds@tycho.nsa.gov>, selinux@tycho.nsa.gov
Subject: Re: Execmem boolean
Date: Wed, 29 Jun 2005 15:37:09 -0400 [thread overview]
Message-ID: <42C2F865.2040102@redhat.com> (raw)
In-Reply-To: <1120071263.20484.45.camel@celtics.boston.redhat.com>
Ivan Gyurdiev wrote:
>> Strict policy likely
>>shouldn't allow execmod to anything but texrel_shlib_t, and can thus
>>omit the boolean altogether.
>>
>>
>
>Please don't break strict policy :(
>
>I still have some hope left to be able to
>run it on my home machine. The level of "strictness"
>should be configurable.
>
>
>
>We could kill the allow_execmod/allow_execmem booleans,
>allow execmod to texrel, allow exemem for X,
>
>
Ok.
Should be a boolean allow_X_execmem. Most people don't need execmem for
X. (Only nvidia binary drivers)
>and then have per app booleans for other things we don't trust
>(like Java applets?).
>
>
>
>
>
>
--
--
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 prev parent reply other threads:[~2005-06-29 19:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-26 21:42 Execmem boolean Ivan Gyurdiev
2005-06-27 11:59 ` 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 [this message]
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=42C2F865.2040102@redhat.com \
--to=dwalsh@redhat.com \
--cc=ivg2@cornell.edu \
--cc=sds@tycho.nsa.gov \
--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.