Bug 218653 - How to allow execheap for MATLAB?
Summary: How to allow execheap for MATLAB?
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 5
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-12-06 16:46 UTC by Orion Poplawski
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-02-14 15:12:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Orion Poplawski 2006-12-06 16:46:44 UTC
Description of problem:

Seeing:

Dec  5 17:01:02 cappello kernel: audit(1165363262.476:151): avc:  denied  {
execheap } for  pid=4276 comm="MATLAB" scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process

Is there any way other than allow_execheap=1 to give MATLAB execheap permission?

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

Comment 1 Daniel Walsh 2007-02-14 15:07:07 UTC
No.  You could write policy for it.  Sorry about loosing this bug in the stream
of bugzillas.

Comment 2 Daniel Walsh 2007-02-14 15:08:27 UTC
This should really be reported as a bug in MATLAB.

Comment 3 Daniel Walsh 2007-02-14 15:12:27 UTC
One evil hack that you could do would be to assign java_exec_t to the executable.
Jave currently has the execheap permission.

Comment 4 Orion Poplawski 2007-02-14 16:53:09 UTC
Not a bad idea actually, since I think it is the Java parts of matlab that's
causing the problem.

Comment 5 Daniel Walsh 2007-02-14 20:17:09 UTC
What is the path to matlab?

Comment 6 Orion Poplawski 2007-02-16 18:55:10 UTC
Well, that's tricky because you can install it anywhere.  In our case, we
install it on our NFS server which causes problems with SELinux.  Or in
/opt/local/matlab on our laptops, or at least symbolic links are there that
point to the real install in /export/local/matlab_r2006a (or whatever version).
 The binary is then in some location like /opt/local/matlab/bin/<arch>/MATLAB.

Also, looks likes this is in the policy:

/usr/local/matlab.*/bin/glnx86/libmwlapack\.so --
system_u:object_r:textrel_shlib_t:s0

I've added the following as well:

/export/local/matlab.*/sys/os/glnx86/libtermcap.so   
system_u:object_r:textrel_shlib_t:s0
/export/local/matlab.*/bin/glnx86/(libmw(lapack|mathutil|services)|lapack|libmkl).so
   system_u:object_r:textrel_shlib_t:s0



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