[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Execmem boolean

To: Daniel J Walsh <dwalsh@xxxxxxxxxx>
Subject: Re: Execmem boolean
From: Stephen Smalley <sds@xxxxxxxxxxxxx>
Date: Wed, 29 Jun 2005 15:58:20 -0400
Cc: ivg2@xxxxxxxxxxx, selinux@xxxxxxxxxxxxx
In-reply-to: <42C2F865.2040102@xxxxxxxxxx>
Organization: National Security Agency
References: <1119822163.4357.9.camel@xxxxxxxxxxxxxxxxxxxxx> <1119883756.32316.74.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <42C2DB70.2070204@xxxxxxxxxx> <1120070997.3553.172.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <1120071263.20484.45.camel@xxxxxxxxxxxxxxxxxxxxxxxxx> <42C2F865.2040102@xxxxxxxxxx>
Sender: owner-selinux@xxxxxxxxxxxxx

On Wed, 2005-06-29 at 15:37 -0400, Daniel J Walsh wrote:
> Ok.
> Should be a boolean allow_X_execmem.  Most people don't need execmem for 
> X.  (Only nvidia binary drivers)

I've seen it with other (open source) drivers too.

-- 
Stephen Smalley
National Security Agency


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with
the words "unsubscribe selinux" without quotes as the message.

References:
- Execmem boolean
  - From: Ivan Gyurdiev
- Re: Execmem boolean
  - From: Stephen Smalley
- Re: Execmem boolean
  - From: Daniel J Walsh
- Re: Execmem boolean
  - From: Stephen Smalley
- Re: Execmem boolean
  - From: Ivan Gyurdiev
- Re: Execmem boolean
  - From: Daniel J Walsh

Prev by Date: RE: file contexts and modularity
Next by Date: RE: file contexts and modularity
Previous by thread: Re: Execmem boolean
Next by thread: Re: Execmem boolean
Index(es):
- Date
- Thread

This mailing list archive is a service of Copilot Consulting.