+++ This bug was initially created as a clone of Bug #843730 +++ In SSSD there is a new feature which writes SSSD config files into /etc/selinux/<policy>/logins/ for SELinux PAM module which then uses this information to set correct context for remote user logging in. I'd like to ask for update of SELinux policy so SSSD can write into this directory. I've set permissive mode on my machine, tried to log in several times and these are the rules that audit2allow returned: allow sssd_t selinux_config_t:dir { write remove_name add_name }; allow sssd_t selinux_config_t:file { write rename create unlink }; Please note that we don't write directly to final config files but we rather use mkstemp-style temporary files which are then renamed to the final name. --- Additional comment from jzeleny on 2012-07-27 10:12:27 CEST --- There is one mistake in my initial description. SSSD of course writes SELinux config files into /etc/selinux/<policy>/logins/, not SSSD config files.
We added fixes to Fedora. Let's wait to see if this works correctly.
*** Bug 848751 has been marked as a duplicate of this bug. ***
Backported to RHEL6.4.
# matchpathcon /etc/selinux/targeted/logins//etc/selinux/targeted/logins system_u:object_r:selinux_login_config_t:s0 # sesearch -s sssd_t -t selinux_login_config_t -c file --allow Found 1 semantic av rules: allow sssd_t selinux_login_config_t : file { ioctl read write create getattr setattr lock append unlink link rename open } ; # sesearch -s sssd_t -t selinux_login_config_t -c dir --allow Found 1 semantic av rules: allow sssd_t selinux_login_config_t : dir { ioctl read write getattr lock add_name remove_name search open } ; #
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-0314.html