Bug 989148
Summary: | SELinux is preventing /usr/bin/dbus-daemon from 'associate' accesses on the shared memory . | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | erwincas <erwincas> |
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: | 19 | CC: | dominick.grift, dwalsh, eparis, erwincas, mgrepl, sdsmall |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | abrt_hash:1f3a81ece012adf7a7059afdef6cf8fa74246d6392d0eff25d7209b7ec6cf048 | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-02-18 14:02:28 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
erwincas
2013-07-27 22:45:18 UTC
What process is running as initrc_t? ps -eZ | grep initrc_t ConsoleKit? (In reply to Miroslav Grepl from comment #1) > What process is running as initrc_t? > > ps -eZ | grep initrc_t system_u:system_r:initrc_t:s0 978 ? 00:00:00 esets_daemon system_u:system_r:initrc_t:s0 980 ? 00:00:26 esets_daemon system_u:system_r:initrc_t:s0 981 ? 00:00:00 esets_mac Where does esets_daemon come from? (In reply to Miroslav Grepl from comment #4) > Where does esets_daemon come from? It comes from Eset Nod32 Antivirus for linux Ver 4. Did anything break? (In reply to Daniel Walsh from comment #6) > Did anything break? nothing, everything runs fine, just the messages at every startup. What is weird here is system_dbusd_t only associates with its own shared memory. sesearch -A -s system_dbusd_t -c shm Found 1 semantic av rules: allow system_dbusd_t system_dbusd_t : shm { create destroy getattr setattr read write associate unix_read unix_write lock } ; According to policy anyways. If shmget is called with a key that is not IPC_PRIVATE and the key already exists, then it can yield an identifier for a pre-existing segment created by another process. Output of ipcs -m -p might be interesting, along with ps entries for the pids displayed in the ipcs output. 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. |