SELinux is preventing nspluginviewer from changing a writable memory segment
executable.
Detailed Description:
The nspluginviewer 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
(http://people.redhat.com/drepper/selinux-mem.html) web page explains how to
remove this requirement. If nspluginviewer does not work and you need it to
work, you can configure SELinux temporarily to allow this access until the
application is fixed. Please file a bug report
(http://bugzilla.redhat.com/bugzilla/enter_bug.cgi) against this package.
Allowing Access:
If you trust nspluginviewer to run correctly, you can change the context of the
executable to unconfined_execmem_exec_t. "chcon -t unconfined_execmem_exec_t
'/usr/bin/nspluginviewer'". You must also change the default file context files
on the system in order to preserve them even on a full relabel. "semanage
fcontext -a -t unconfined_execmem_exec_t '/usr/bin/nspluginviewer'"
Source Context unconfined_u:unconfined_r:unconfined_t:SystemLow-
SystemHigh
Target Context unconfined_u:unconfined_r:unconfined_t:SystemLow-
SystemHigh
Target Objects None [ process ]
Source nspluginviewer
Source Path /usr/bin/nspluginviewer
Port <Unknown>
Host localhost.localdomain
Source RPM Packages kdebase-4.1.0-1.fc10
Target RPM Packages
Policy RPM selinux-policy-3.5.1-4.fc10
Selinux Enabled True
Policy Type targeted
MLS Enabled True
Enforcing Mode Enforcing
Plugin Name allow_execmem
Host Name localhost.localdomain
Platform Linux localhost.localdomain 2.6.26.1 #1 SMP Sat
Aug 2 21:36:01 CDT 2008 i686 i686
Alert Count 29
First Seen Sun 03 Aug 2008 12:55:21 PM CDT
Last Seen Sun 03 Aug 2008 12:55:21 PM CDT
Local ID 865503d3-baab-4dcd-adc0-47f8fff6ade6
Line Numbers
I have recently installed xine(xine-lib-1.1.15 and xine-ui from source) and I got this one immediately following:
What should I do? Should I just apply the fix and move on?
Summary:
SELinux is preventing xine from making the program stack executable.
Detailed Description:
The xine application attempted to make its stack executable. This is a potential
security problem. This should never ever be necessary. Stack memory is not
executable on most OSes these days and this will not change. Executable stack
memory is one of the biggest security problems. An execstack error might in fact
be most likely raised by malicious code. Applications are sometimes coded
incorrectly and request this permission. The SELinux Memory Protection Tests
(http://people.redhat.com/drepper/selinux-mem.html) web page explains how to
remove this requirement. If xine does not work and you need it to work, you can
configure SELinux temporarily to allow this access until the application is
fixed. Please file a bug report
(http://bugzilla.redhat.com/bugzilla/enter_bug.cgi) against this package.
Allowing Access:
Sometimes a library is accidentally marked with the execstack flag, if you find
a library with this flag you can clear it with the execstack -c LIBRARY_PATH.
Then retry your application. If the app continues to not work, you can turn the
flag back on with execstack -s LIBRARY_PATH. Otherwise, if you trust xine to run
correctly, you can change the context of the executable to
unconfined_execmem_exec_t. "chcon -t unconfined_execmem_exec_t '/usr/bin/xine'"
You must also change the default file context files on the system in order to
preserve them even on a full relabel. "semanage fcontext -a -t
unconfined_execmem_exec_t '/usr/bin/xine'"
I'm guessing these are one in the same? Did it install xine as a plugin
to firefox? This is a xine bug. execstack is never right. Did you try
following the suggestion and run execstack -c LIBRARY_PATH on all of the
libraries installed by xine-libs?
-Eric
--
fedora-selinux-list mailing list
fedora-selinux-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-selinux-list
selinux - nspluginscan, and xine denials
