Bug 611308
| Summary: | MediaWiki's ulimit4.sh triggers SELinux warnings when thumbnailing | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Joel Uckelman <uckelman> |
| Component: | selinux-policy-targeted | Assignee: | Miroslav Grepl <mgrepl> |
| Status: | CLOSED WONTFIX | QA Contact: | Ben Levenson <benl> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 13 | ||
| 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: | 2011-06-27 19:25:49 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
Joel Uckelman
2010-07-04 19:55:34 UTC
You can add these rules for now using # grep avc /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp I think it might be best to add policy for mediawiki. We really do not want to start granting setrlimit to all apache processes. Actually Miroslav lets add a boolean. ## <desc> ## <p> ## Allow httpd daemon to change system limits ## </p> ## </desc> gen_tunable(httpd_setrlimit, false) tunable_policy(`httpd_setrlimit',` allow httpd_t self:process setrlimit; ') Fixed in selinux-policy-3.7.19-36.fc13 This seems not to work: 1. I got this error messasge when I installed selinux-policy-targeted-3.7.19-36.fc13: /etc/selinux/targeted/contexts/files/file_contexts: Multiple different specifications for /usr/libexec/telepathy-sofiasip (system_u:object_r:telepathysofiasip_exec_t:s0 and system_u:object_r:telepathy_sofiasip_exec_t:s0). /etc/selinux/targeted/contexts/files/file_contexts: Invalid argument libsemanage.semanage_install_active: setfiles returned error code 1. semodule: Failed! 2. setsebool -P httpd_setrlimit 1 libsemanage.dbase_llist_set: record not found in the database libsemanage.dbase_llist_set: could not set record value Could not change boolean httpd_setrlimit Could not change policy booleans 3. The new boolean isn't documented in httpd_selinux(8). I am fixing this issue. Please run # semodule -r telepathysofiasip and then install selinux-policy-targeted package from Koji again. Thanks. Updated selinux-policy packages will be available today. It seems to work now. Thanks. selinux-policy-3.7.19-37.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/selinux-policy-3.7.19-37.fc13 Hmm. Now that I've had time to test a bit more, I can see that turning on httpd_setrlimit causes a new problem: There's no SELinux denials now, but when ulimit4.sh calls convert, now it seg faults! This is 100% repeatable with httpd_setrlimit turned on, and never happens with httpd_setrlimit turned off (that is, convert always makes the image thumbnail properly). Here's what I see in my apache error_log: /usr/share/mediawiki/bin/ulimit4.sh: line 4: 12339 Segmentation fault (core dumped) '/usr/bin/convert' -quality 80 -background white -size 120 '/var/www/mediawiki/images/3/3f/Space_infantry_screenshot.jpg' -thumbnail '120x81!' -depth 8 -sharpen '0x0.4' '/var/www/mediawiki/images/thumb/3/3f/Space_infantry_screenshot.jpg/120px-Space_infantry_screenshot.jpg' 2>&1 The crash of convert is reported in Bug 614638. selinux-policy-3.7.19-37.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update selinux-policy'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/selinux-policy-3.7.19-37.fc13 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 Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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. Thank you for reporting this bug and we are sorry it could not be fixed. |