Bug 1546423
| Summary: | SELinux is preventing bluetoothd from 'create' accesses on the socket Unknown. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jo00 <jokarsp1> |
| Component: | selinux-policy | Assignee: | Lukas Vrabec <lvrabec> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 27 | CC: | dineshsivajirao, dwalsh, Jasper.Hartline, lvrabec, markuzvelazquez, me+redhat, mgrepl, nicole, plautrba, pmoore, wim.vd.woude |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | abrt_hash:9a1917dd081d24056baf33f725215afd6adf9e88f0c87654e0c1a4b222d5233b;VARIANT_ID=workstation; | ||
| Fixed In Version: | selinux-policy-3.13.1-283.28.fc27 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-03-20 18:17:08 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 of problem: Opened a browser window on Chrome Version-Release number of selected component: selinux-policy-3.13.1-283.24.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.13.9-300.fc27.x86_64 type: libreport *** Bug 1548855 has been marked as a duplicate of this bug. *** Description of problem: I do not know how this issue happened. The message started showing up a few days ago. Version-Release number of selected component: selinux-policy-3.13.1-283.24.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.5.7-200.fc23.x86_64 type: libreport Description of problem: I execute several time the solution proposed by SELinux Alert Browser which is : You should report this as a bug. You can generate a local policy module to allow this access. Allow this access for now by executing: # ausearch -c 'bluetoothd' --raw | audit2allow -M my-bluetoothd # semodule -X 300 -i my-bluetoothd.pp but even after a reboot the message still appear and bluetooth is unsuable. Version-Release number of selected component: selinux-policy-3.13.1-283.26.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.13.9-300.fc27.x86_64 type: libreport Description of problem: Problem first occurred after updating the fresh installation of Fedora 27, at next reboot first warning about Selinux - Bluetooth Version-Release number of selected component: selinux-policy-3.13.1-283.26.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.13.9-300.fc27.x86_64 type: libreport selinux-policy-3.13.1-283.28.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-32ebae3424 selinux-policy-3.13.1-283.28.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-32ebae3424 selinux-policy-3.13.1-283.28.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-32ebae3424 Description of problem: Es la primera vez que instalo este Sistema Operativo, al terminar la instalacion se detecto este bug. Version-Release number of selected component: selinux-policy-3.13.1-283.14.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.13.9-300.fc27.x86_64 type: libreport selinux-policy-3.13.1-283.28.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report. |
Description of problem: SELinux is preventing bluetoothd from 'create' accesses on the socket Unknown. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that bluetoothd should be allowed create access on the Unknown socket by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # ausearch -c 'bluetoothd' --raw | audit2allow -M my-bluetoothd # semodule -X 300 -i my-bluetoothd.pp Additional Information: Source Context system_u:system_r:init_t:s0 Target Context system_u:system_r:init_t:s0 Target Objects Unknown [ socket ] Source bluetoothd Source Path bluetoothd Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-283.24.fc27.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.13.9-300.fc27.x86_64 #1 SMP Mon Oct 23 13:41:58 UTC 2017 x86_64 x86_64 Alert Count 2 First Seen 2018-02-17 01:33:22 IST Last Seen 2018-02-17 01:33:22 IST Local ID e9090f12-136d-4460-96e0-90584f47b70f Raw Audit Messages type=AVC msg=audit(1518824002.709:386): avc: denied { create } for pid=5041 comm="bluetoothd" scontext=system_u:system_r:init_t:s0 tcontext=system_u:system_r:init_t:s0 tclass=socket permissive=0 Hash: bluetoothd,init_t,init_t,socket,create Version-Release number of selected component: selinux-policy-3.13.1-283.24.fc27.noarch Additional info: component: selinux-policy reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.13.9-300.fc27.x86_64 type: libreport Potential duplicate: bug 1494924