Bug 1813605 - SELinux is preventing sssd from 'read' accesses on the directory NetworkManager.
Summary: SELinux is preventing sssd from 'read' accesses on the directory NetworkManager.
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 30
Hardware: x86_64
OS: Unspecified
Target Milestone: ---
Assignee: Zdenek Pytela
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:e953170f58a2bf1d85965556f66...
Depends On:
TreeView+ depends on / blocked
Reported: 2020-03-14 19:10 UTC by John Griffiths
Modified: 2020-05-26 18:43 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-05-26 18:43:38 UTC
Type: ---

Attachments (Terms of Use)

Description John Griffiths 2020-03-14 19:10:36 UTC
Description of problem:
Installed new version of sssd with update.
SELinux is preventing sssd from 'read' accesses on the directory NetworkManager.

*****  Plugin catchall (100. confidence) suggests   **************************

If you believe that sssd should be allowed read access on the NetworkManager directory by default.
Then 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 'sssd' --raw | audit2allow -M my-sssd
# semodule -X 300 -i my-sssd.pp

Additional Information:
Source Context                system_u:system_r:sssd_t:s0
Target Context                system_u:object_r:NetworkManager_var_run_t:s0
Target Objects                NetworkManager [ dir ]
Source                        sssd
Source Path                   sssd
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
Policy RPM                    selinux-policy-3.14.3-56.fc30.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 5.5.8-100.fc30.x86_64 #1 SMP Thu
                              Mar 5 21:55:51 UTC 2020 x86_64 x86_64
Alert Count                   1
First Seen                    2020-03-14 12:41:40 EDT
Last Seen                     2020-03-14 12:41:40 EDT
Local ID                      3b4bcb57-552d-48f2-9f8a-82bb7e0b53c8

Raw Audit Messages
type=AVC msg=audit(1584204100.678:6111): avc:  denied  { read } for  pid=19658 comm="sssd" name="NetworkManager" dev="tmpfs" ino=24551 scontext=system_u:system_r:sssd_t:s0 tcontext=system_u:object_r:NetworkManager_var_run_t:s0 tclass=dir permissive=0

Hash: sssd,sssd_t,NetworkManager_var_run_t,dir,read

Version-Release number of selected component:

Additional info:
component:      selinux-policy
reporter:       libreport-2.12.0
hashmarkername: setroubleshoot
kernel:         5.5.8-100.fc30.x86_64
type:           libreport

Potential duplicate: bug 1810404

Comment 1 Zdenek Pytela 2020-03-16 10:39:02 UTC
Thank you for reporting the issue,

I've submitted a Fedora PR to backport the existing fix to F30:


Comment 2 Ben Cotton 2020-04-30 20:11:21 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-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 '30'.

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 30 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.

Comment 3 Ben Cotton 2020-05-26 18:43:38 UTC
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.