Bug 1098728
| Summary: | selinux prevents installing to ~/bin | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | RIchard Gladman <rhbugzilla> | ||||
| Component: | libselinux | Assignee: | Miroslav Grepl <mgrepl> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 20 | CC: | dwalsh, mgrepl, rjt | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-06-29 20:40:36 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: | |||||||
| Attachments: |
|
||||||
|
Description
RIchard Gladman
2014-05-17 18:58:29 UTC
I've just encountered exactly the same issue, oddly enough also attempting to install Komodo IDE. Thanks for the detailed bug report; I was easily able to install the software by following your instructions. Is the Komodo IDE doing somekind of semanage command or setsebool when you install it? I wonder if it has something to do with the umask you are running with when running these commands. My umask was set to 0022. install.sh invokes a Python script, which does make use of an SELinux lib (written by ActiveState). I haven't trawled through the code to see what it does (I'm not very fluent in Python). So, probably this is a Komodo bug, not a Fedora one. Is it worth me attaching these Python scripts for someone to review? # umask 0022 # semanage fcontext -a -t etc_t /dan # ls -lZ /etc/selinux/targeted/contexts/files/file_contexts*bin -rw-------. 1 root root staff_u:object_r:file_context_t:s0 1396370 Aug 16 06:45 /etc/selinux/targeted/contexts/files/file_contexts.bin -rw-------. 1 root root staff_u:object_r:file_context_t:s0 182739 Aug 16 06:45 /etc/selinux/targeted/contexts/files/file_contexts.homedirs.bin -rw-------. 1 root root staff_u:object_r:file_context_t:s0 1916 Aug 16 06:45 /etc/selinux/targeted/contexts/files/file_contexts.local.bin No it is a umask problem. We need to change libselinux to override the mask. Created attachment 927881 [details]
This patch will make file_context.*.bin match the permissions of the source
I also reported this to Activestate so they would be aware of the issue and hopefully fix anything needing fixing at their end. This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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. Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |