Bug 523874
Summary: | setroubleshoot: SELinux is preventing /usr/bin/nautilus from making the program stack executable. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dawid Zamirski <dzrudy> |
Component: | nautilus | Assignee: | Tomáš Bžatek <tbzatek> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | dwalsh, jkubin, kmaraas, lordstenka, mclasen, mgrepl, tbzatek, tsmetana |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | setroubleshoot_trace_hash:59ef4353b89d312b527e6d8076ef57c6b033af0e6a05240ff5b785975b33b56f | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-10-01 13:24:37 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
Dawid Zamirski
2009-09-16 23:40:55 UTC
Nautilus should not require execstack/execmem http://people.redhat.com/~drepper/selinux-mem.html Dawid, If this is actually causing things to blow up you can turn on the allow_execstack boolean. setsebool -P allow_execstack 1 Daniel, I've filled this bug via the ABRT in SETroubleshoot after I updated my rawhide install to latest policy and relabel on boot. I'm running SELinux in permissive mode so everything works well except I get the warnings sometimes. I know it's rawhide and things like that may happen often and I generally do not file BZ as it might be fixed in the next 'yum update'. I saw this particular alert since about a week so I thought it might be useful to BZ it. Yes this is very useful. Ordinarily during Fedora 11 we ran with the allow_execstack boolean turned on, because of buggy apps, We are trying to make sure no apps in F12 that we ship require this priv, since it is somewhat dangerous. Hmm. Dan, is there any way to get a stacktrace from when this happens ? Dawid, do you have any nautilus plugins installed ? Say, nautilus-open-terminal or nautilus-actions ? I guess you could ask the reporter to run strace on nautilus and try to get it to repeat. He is probably seeing a mprot failure. Of course since he is in permissive mode there will be no error in strace. Yes, I've got these installed: nautilus.x86_64 2.28.0-2.fc12 @rawhide nautilus-actions.x86_64 1.12.0-1.fc12 @rawhide nautilus-extensions.x86_64 2.28.0-2.fc12 @rawhide nautilus-open-terminal.x86_64 0.17-2.fc12 @rawhide nautilus-search-tool.x86_64 0.3.0-3.fc12 @rawhide nautilus-sendto.x86_64 2.28.0-1.fc12 @rawhide I also have seen this alert with epiphany (2.27.x - I did not get today's update yet) and chromium (it's not in fedora). Since I run in permissive mode, this is not a problem for me now but when final Fedora is released I'll switch to enforcing mode. I know that we Fedora does not support software that does not come from official repos (like the chromium) but I still would prefer to keep the SELinux boolean on. So now finally is my question: Is it feasible to enable exclusion of certain binaries from execmem,stack etc protections and yet keep the global flag on so that I can exclude eg chromium from the protection and keep the rest of the system protected? PS. I'll run nautilus with strace as soon as I get back home from work :-) Once you've figured out how to reproduce this and detect it in strace, you could remove the extensions one-by-one to see which one causes this. Dawid, please note that not only nautilus-* packages provide extensions for nautilus, see the contents of /usr/lib64/nautilus/extensions-2.0 directory. *** Bug 524446 has been marked as a duplicate of this bug. *** It seems that this has somehow fixed itself as I'm not getting this alert anymore since about a week. Previously I was getting at least one such warning per day and now nothing.. I did not change any booleans and I did not remove any of nautilus-related packages - just daily yum update. Ok I can go with a miracle. I will close for now and reopen if it happens again. |