Bug 207103 - Xine from Freshrpms: avc: denied { execmod } for pid=7892 comm="xine" name="libfame-0.9.so.1.0.0"
Xine from Freshrpms: avc: denied { execmod } for pid=7892 comm="xine" name...
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: selinux-policy (Show other bugs)
5
All Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-09-19 09:32 EDT by Andre Robatino
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version: Current
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-03-28 16:06:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Andre Robatino 2006-09-19 09:32:27 EDT
Description of problem:
  When running Xine from Freshrpms, the following message appears in
/var/log/messages:

Sep 19 08:56:40 localhost kernel: audit(1158670600.027:6): avc:  denied  {
execmod } for  pid=7892 comm="xine" name="libfame-0.9.so.1.0.0" dev=dm-0 ino=8481188
scontext=user_u:system_r:unconfined_execmem_t:s0
tcontext=system_u:object_r:lib_t:s0 tclass=file

Libfame is also a Freshrpms package.  The offending file is:

[andre@localhost ~]$ ls -lZ /usr/lib/sse2/libfame-0.9.so.1.0.0
-rwxr-xr-x  root root system_u:object_r:lib_t         
/usr/lib/sse2/libfame-0.9.so.1.0.0

  I'm not sure if this should be reported under Fedora or Freshrpms.

Version-Release number of selected component (if applicable):
selinux-policy-2.3.7-2.fc5

How reproducible:
always
Comment 1 Daniel Walsh 2006-09-19 10:42:22 EDT
Report the bug to libfame developer.

You need to set the context of the file to textrel_shlib_t to make it work

chcon -t textrel_shlib_t /usr/lib/sse2/libfame-0.9.s0.1.0.0

Fixed in selinux-policy-2.3.14-4
Comment 2 Daniel Walsh 2007-03-28 16:06:30 EDT
Closing bugs

Note You need to log in before you can comment on or make changes to this bug.