Bug 467054

Description of problem:
The nexuiz-sdl application attempted to change the access protection of memory (e.g., allocated using malloc). This is a potential security problem. Applications should not be doing this. Applications are sometimes coded incorrectly and request this permission. The SELinux Memory Protection Tests web page explains how to remove this requirement. If nexuiz-sdl does not work and you need it to work, you can configure SELinux temporarily to allow this access until the application is fixed.

Version-Release number of selected component (if applicable):
Name       : nexuiz
Arch       : x86_64
Version    : 2.4.2
Release    : 3.fc10

How reproducible:
SELinux configured like this:
System Default Enforcing Mode = Enforcing
Current Enforcing Mode = Enforcing
System Default Policy Type = Targeted

Steps to Reproduce:
1. Enable SELinux as it's shown above
2. Login into the Gnome desktop
3. Run Nexuiz
  
Actual results:
Nexuiz did not start and SELinux TroubleShooter shows this message: SELinux is preventing nexuiz-sdl from changing a writable memory segment executable.

Expected results:
Nexuiz starts correctly.

Additional info:
In Fedora 9 was everything OK.
Now in Fedora 10 I'm using this workaround:
chcon -t unconfined_execmem_exec_t '/usr/bin/nexuiz-sdl'

Similar problems:
https://bugzilla.redhat.com/show_bug.cgi?id=467033
https://bugzilla.redhat.com/show_bug.cgi?id=467034
https://bugzilla.redhat.com/show_bug.cgi?id=467035