Bug 1298726
| Summary: | third-party (Brother) drivers blocked by SELinux | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jehan <jehan.marmottard> |
| Component: | selinux-policy | Assignee: | Lukas Vrabec <lvrabec> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 26 | CC: | bmason, dwalsh, jpopelka, lvrabec, mgrepl, nobody+bjmason, plautrba, pmoore, ppywlkiqletw, twaugh |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | selinux-policy-3.14.2-15.fc29 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-05-29 12:08:05 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Attachments: | |||
|
Description
Jehan
2016-01-14 20:18:54 UTC
Created attachment 1123533 [details] SELinux alert: brcupsconfpt1 tries to execute /etc/ld.so.cache Ok. After weeks, I finally understood what was the problem. The print jobs were blocked by SELinux. I understood this after noticing an alert icon appearing in the bottom left bar (GNOME 3). Following indications in details, I fixed by running: > sudo setsebool -P cups_execmem 1 Following indications of SELinux which says "If you believe that brcupsconfpt1 should be allowed execmem access on processes labeled cupsd_t by default." I leave the bug report opened though because this is not user-friendly, especially when you buy a printer with linux drivers! I have installed official Brother drivers, which has explicit support of Linux. This is rare and cool enough in printer makers for Linux distributions to not block these, right? So I know these RPM are not made by the Fedora community, hence they are not in the official package repository. But it would be great if they were, and if not, could we "plan" for the possibility of these being installed by the user, and having SELinux not blocking its normal functioning? Also I will note that the CUPSWrapper printer drivers is GPLv2. All other drivers (LPR printer, scanner, scan-key tool, fax…) use some kind of "AS IS" license. I can't see if it corresponds to any known Free license (I don't know them all by heart) but it seems to be pretty much some kind of Free license anyway. Extract from it: > Brother grants User a non-exclusive license: to reproduce and/or distribute (via Internet or in any other manner) the Software. Further, Brother grants User a non-exclusive license to modify, alter, translate or otherwise prepare derivative works of the Software and to reproduce and distribute (via Internet or in any other manner) such modification, alteration, translation or other derivative works for any purpose. Disclaimer: I'm not a lawyer. I propose you have a look at any of the official Brother RPMs. Just before every download, the license is displayed. In any case, it looks to me like we could have these redistributed in the Fedora package repository. No? Created attachment 1123534 [details]
Text when clicking on "Details" button in SELinux dialog.
Attached the text from SELinux when clicking "Details" button after receiving the alert. In case it is useful.
Created attachment 1128570 [details]
SELinux alert: brprintconf_mc tries to execute /etc/ld.so.cache
Additional info: even though now, I can print, I noticed that SELinux outputted another alert when trying to print, this time on brprintconf_mc, which also tried to execute /etc/ld.so.cache.
It did not prevent printing, but maybe it blocks some of my printer feature which I would discover later along the road?
Anyway I leave here the info for you to evaluate what brprintconf_mc does.
Thanks!
Created attachment 1128571 [details]
Contents of "Details" with the second alert.
And the contents when clicking "Details" button on this second alert.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. Note: I installed Fedora 24 and the problem still exists there. This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 EOL if it remains open with a Fedora 'version' of '23'. 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 23 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. Moving to Fedora 24 based on Comment #6. This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 EOL if it remains open with a Fedora 'version' of '24'. 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 24 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. Moving to Fedora 25. Issue is being fixed in bugzilla 1478602 This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 EOL if it remains open with a Fedora 'version' of '25'. 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 25 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. Last I tried, the issue was still happening in Fedora 26. Comment 12 seems to indicate this has been fixed in Fedora 26 though. I'm not sure, I'll have to try soon. But for the time being, I'll bump the version on the bug report. Despite the changes introduced by Bug 1478602, this still isn't completely resolved in Fedora 26, and my QL-570 won't print unless I "setenforce permissive" before printing something. The audit message is now: type=AVC msg=audit(1520890850.331:60004): avc: denied { execute } for pid=31610 comm="rastertobrpt1" path="/var/tmp/Stdshared2005102601" dev="dm-3" ino=2729 scontext=system_u:system_r:cupsd_t:s0-s0:c0.c1023 tcontext=system_u:object_r:cupsd_tmp_t:s0 tclass=file permissive=1 Ok, it is really selinux issue, reassigning to selinux policy. This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 EOL if it remains open with a Fedora 'version' of '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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. |