Bug 650279
| Summary: | SELinux is preventing /usr/lib64/maxima/5.22.1/binary-gcl/maxima from changing the access protection of memory on the heap. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Rex Dieter <rdieter> |
| Component: | gcl | Assignee: | Jerry James <loganjerry> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | rawhide | CC: | dwalsh, green, loganjerry, mgrepl |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | setroubleshoot_trace_hash:b6f935610f91c725a2c016f30ee8f80916f9c4e5e7c71fd7b7aaa0224d1e53c3 | ||
| Fixed In Version: | gcl-2.6.8-0.8.20110516cvs.fc14 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-06-07 04:38:40 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Rex Dieter
2010-11-05 16:45:11 UTC
Hrm, tried installing gcl-selinux which is supposed to contain policy to correct this, but it doesn't seem to help. ?? Fwiw, original bug about this was awhile back in bug #496124 It would appear the policy needs apply to /usr/lib/maxima/[^/]+/binary-gcl/maxima /usr/lib64/maxima/[^/]+/binary-gcl/maxima not just /usr/lib/maxima/[^/]+/binary-gcl /usr/lib64/maxima/[^/]+/binary-gcl which is a directory (unless these policies can be made to be recursive?). Though, after making that change, I encounter this, /usr/sbin/semodule -i /usr/share/selinux/packages/gcl/gcl.pp /etc/selinux/targeted/contexts/files/file_contexts: Multiple different specifications for /usr/lib/maxima/[^/]+/binary-gcl/maxima (system_u:object_r:gcl_exec_t:s0 and system_u:object_r:textrel_shlib_t:s0). /etc/selinux/targeted/contexts/files/file_contexts: Multiple different specifications for /usr/lib64/maxima/[^/]+/binary-gcl/maxima (system_u:object_r:gcl_exec_t:s0 and system_u:object_r:textrel_shlib_t:s0). /etc/selinux/targeted/contexts/files/file_contexts: Invalid argument We have those defined as textrel_shlib_t, should I remove. Yes, those need to be gcl_exec_t. With respect to comment 3, my understanding is that I'm specifying a regular expression, so the existing regexps: /usr/lib/maxima/[^/]+/binary-gcl /usr/lib64/maxima/[^/]+/binary-gcl DO match these already: /usr/lib/maxima/[^/]+/binary-gcl/maxima /usr/lib64/maxima/[^/]+/binary-gcl/maxima Is that correct? If so, I should probably just combine those into one rule: /usr/lib(64)?/maxima/[^/]+/binary-gcl /usr/lib(64)?/maxima/[^/]+/binary-gcl Will not match an executable that ends with maxima. Miroslav, remove the maxima lines from our policy. /usr/lib/maxima/[^/]+/binary-gcl/maxima -- gen_context(system_u:object_r:textrel_shlib_t,s0) /usr/lib64/maxima/[^/]+/binary-gcl/maxima -- gen_context(system_u:object_r:textrel_shlib_t,s0) Ok, removed. This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Oops, sorry Rex. I let this fall off my radar. I've got the trivial fix to the SELinux policy and a few more fixes checked into git and a build is on the way once the builders are back online. gcl-2.6.8-0.8.20110516cvs.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/gcl-2.6.8-0.8.20110516cvs.fc15 gcl-2.6.8-0.8.20110516cvs.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/gcl-2.6.8-0.8.20110516cvs.fc14 Package gcl-2.6.8-0.8.20110516cvs.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gcl-2.6.8-0.8.20110516cvs.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/gcl-2.6.8-0.8.20110516cvs.fc15 then log in and leave karma (feedback). gcl-2.6.8-0.8.20110516cvs.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. gcl-2.6.8-0.8.20110516cvs.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report. |