+++ This bug was initially created as a clone of Bug #813959 +++ Description of problem: Files in /etc/BackupPC have context httpd_sys_rw_content_t which restorecon wants to set to httpd_sys_script_rw_t but doesn't succeed. Version-Release number of selected component (if applicable): BackupPC-3.2.1-7.fc16.i686 selinux-policy-3.10.0-80.fc16.noarch selinux-policy-targeted-3.10.0-80.fc16.noarch How reproducible: Always. Actual results: | [root@passepartout ~]# restorecon -Rv /etc/BackupPC | restorecon reset /etc/BackupPC context system_u:object_r:httpd_sys_rw_content_t:s0->system_u:object_r:httpd_sys_script_rw_t:s0 | restorecon reset /etc/BackupPC/config.pl context system_u:object_r:httpd_sys_rw_content_t:s0->system_u:object_r:httpd_sys_script_rw_t:s0 | restorecon reset /etc/BackupPC/hosts context system_u:object_r:httpd_sys_rw_content_t:s0->system_u:object_r:httpd_sys_script_rw_t:s0 | [root@passepartout ~]# restorecon -Rv /etc/BackupPC | restorecon reset /etc/BackupPC context system_u:object_r:httpd_sys_rw_content_t:s0->system_u:object_r:httpd_sys_script_rw_t:s0 | restorecon reset /etc/BackupPC/config.pl context system_u:object_r:httpd_sys_rw_content_t:s0->system_u:object_r:httpd_sys_script_rw_t:s0 | restorecon reset /etc/BackupPC/hosts context system_u:object_r:httpd_sys_rw_content_t:s0->system_u:object_r:httpd_sys_script_rw_t:s0 | [root@passepartout ~]# Expected results: restorecon should succeed. Additional info: | [root@passepartout ~]# semanage -o - | boolean -D | boolean -1 fcron_crond | boolean -1 httpd_enable_homedirs | login -D | login -a -s unconfined_u -r 's0-s0:c0.c1023' __default__ | login -a -s unconfined_u -r 's0-s0:c0.c1023' root | login -a -s system_u -r 's0-s0:c0.c1023' system_u | user -D | port -D | interface -D | node -D | fcontext -D | [root@passepartout ~]# --- Additional comment from mgrepl on 2012-04-20 13:20:34 BST --- It needs to be fixed in the BackupPC policy.
Are you saying that it shouldn't be httpd_sys_script_rw_t or that restorecon does not restore the context? I think you mean the 2nd, but your statement of "onfusion between httpd_sys_rw_content_t and httpd_sys_script_rw_t" confuses me. As far as restorecon, I'm not able to reproduce your output. Please clarify.
Basically from policy and the kernel points of view, they are exactly the same. We have a type alias between them. I believe restorecon is trying to do the right thing, but the kernel notices that they are already set to the same label and thus does nothing.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.