Bug 843814 - Need update of selinux policy related to SSSD
Summary: Need update of selinux policy related to SSSD
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: selinux-policy   
(Show other bugs)
Version: 6.3
Hardware: All
OS: Linux
Target Milestone: rc
: 6.4
Assignee: Miroslav Grepl
QA Contact: Milos Malik
: 848751 (view as bug list)
Depends On: 843730 848751 849567
Blocks: 766000
TreeView+ depends on / blocked
Reported: 2012-07-27 12:26 UTC by Jan Zeleny
Modified: 2013-02-21 08:27 UTC (History)
5 users (show)

Fixed In Version: selinux-policy-3.7.19-160.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 843730
Last Closed: 2013-02-21 08:27:14 UTC
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0314 normal SHIPPED_LIVE selinux-policy bug fix and enhancement update 2013-02-20 20:35:01 UTC

Description Jan Zeleny 2012-07-27 12:26:41 UTC
+++ 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@redhat.com 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.

Comment 1 Miroslav Grepl 2012-08-07 23:43:22 UTC
We added fixes to Fedora. Let's wait to see if this works correctly.

Comment 2 Miroslav Grepl 2012-09-05 05:43:31 UTC
*** Bug 848751 has been marked as a duplicate of this bug. ***

Comment 3 Miroslav Grepl 2012-09-05 06:56:04 UTC
Backported to RHEL6.4.

Comment 5 Milos Malik 2012-10-30 14:21:30 UTC
# 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 } ; 


Comment 7 errata-xmlrpc 2013-02-21 08:27:14 UTC
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.


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