Bug 486755
Summary: | Selinux policy problem with mod_dav_svn | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Roman Kisilenko <rkisilenko> |
Component: | selinux-policy | Assignee: | Miroslav Grepl <mgrepl> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 10 | CC: | dwalsh, jorton, mgrepl, thexman, vanmeeuwen+fedora, vchepkov |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-11-18 11:29:59 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
Roman Kisilenko
2009-02-21 20:24:19 UTC
As workaround solution I am doing following: 1) before commit execute "echo 0 >/selinux/enforce" from root shell 2) commit svn changes 3) after commit execute "echo 1 >/selinux/enforce" from root shell. This is content which httpd processes are expected to have write access to - From reading the httpd_selinux man page, I'm not sure whether content which httpd itself writes to should be labelled: httpd_sys_content_rw_t or whether that is purely for CGI scripts etc. chcon -R -t http_sys_content_rw_t /var/www/svn/repo/db Should fix or you can set the boolean setsebool -P httpd_unified 1 Which will set tell SELinux to treat all apache content the same. Is /var/www/svn/repo/db The standard directory for svn data? Thanks Dan - maybe that could be clarified in httpd_selinux(8), which only talks about httpd_sys_content_rw_t making a different for "httpd_sys_script_exec_t scripts". People are free to put SVN repositories wherever they like, /var/www/svn is just a directory used in the example config. There's no standard here really. Well that is what we want, to setup the default labeling correctly. Are there any other directories under /var/www/svn that need write access? I will update the man page in rawhide. Well, the whole of /var/www/svn would need to be writable by httpd. I can update the example config to mention the labelling. Any reason not to add this to the spec file then we could get it labeled automatically? Miroslav can you add /var/www/svn(/.*)? gen_context(system_u:object_r:httpd_sys_content_rw_t,s0) Do you mean, to package the /var/www/svn directory? Yeah, we could do that. That way when rpm creates it, it will get labeled httpd_sys_content_rw_t automagically. Fixed in selinux-policy-3.5.13-49.fc10 I would like to raise my concerns. not everything under /var/www/svn needs to be writable by server, furthermore, it can be rather dangerous if now you allow web server to create/modify repository hooks under /var/www/svn/hooks. Hello, If you decide to alter default selinux policy to stop marking /var/www/svn/hooks(/.*) as httpd_sys_content_rw_t could you please do the same for /var/www/svn/conf(/.*). It also does not need to be writable by apache. Thank you, Roman /var/www/svn(/.*)? gen_context(system_u:object_r:httpd_sys_script_rw_t,s0) /var/www/svn/hooks(/.*)? gen_context(system_u:object_r:httpd_sys_content_t,s0) /var/www/svn/conf(/.*)? gen_context(system_u:object_r:httpd_sys_content_t,s0) Miroslav can you add these. Hooks should have httpd_sys_script_exec_t context, imho. Ok if they are cgi scripts sounds correct Fixed in selinux-policy-3.5.13-62.fc10 This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. 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 '10'. 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 10'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 10 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 |