Bug 974748
Summary: | SELinux is preventing /usr/sbin/cupsd from 'write' accesses on the file subscriptions.conf.O. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Markus Haybach <markus> |
Component: | cups | Assignee: | Tim Waugh <twaugh> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 19 | CC: | dominick.grift, dwalsh, jpopelka, mgrepl, twaugh |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | abrt_hash:130ae95988abad73a7aa26a6ec2fbad281e7011bfb77379749184021a0f6ffc0 | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-02-17 15:35:33 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
Markus Haybach
2013-06-15 11:01:11 UTC
restorecon -R -v /etc/cups Should fix this. Tim is there any chance of moving cups rw config into a different directory? I have no idea how this content could get mislabeled, since an admin process creating it or cupsd_t creating it would create it with the correct label. Do you think it would help if it were moved? I'm not sure I understand why. Well it might help a little. SELinux labels everything in a directory by default based on the directory label. Since this directory contains both read/only content and read/write content, we label the directory with a read/only label. This can lead to files that should be read/write being accidently labeled with the read/only label causing this AVC. If we had separate directories for /etc/cups and /etc/cups/subscriptions/ Then we could label them differently and it would be less likely that an admin would end up with mislabeled content. That being said with newer file creation policy, we are seeing these kind of issues much less frequently. I am not even sure how this file got mislabeled. If i remove the file and touch it, it gets labeled correctly. This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. |