RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1072067 - SSSD Does not cache SELinux map from FreeIPA correctly
Summary: SSSD Does not cache SELinux map from FreeIPA correctly
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sssd
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: rc
: ---
Assignee: Jakub Hrozek
QA Contact: Kaushik Banerjee
URL:
Whiteboard:
Depends On: 1071578
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-03 20:12 UTC by Jakub Hrozek
Modified: 2020-05-02 17:38 UTC (History)
15 users (show)

Fixed In Version: sssd-1.11.2-54.el7
Doc Type: Bug Fix
Doc Text:
Clone Of: 1071578
Environment:
Last Closed: 2014-06-13 11:01:50 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 3306 0 None None None 2020-05-02 17:38:56 UTC

Description Jakub Hrozek 2014-03-03 20:12:22 UTC 
+++ This bug was initially created as a clone of Bug #1071578 +++

Description of problem:
FreeIPA allows the user to create a set of SELinux user maps. These are not cached properly, and as a result for a user with a domain joined system such as a laptop, when the system is started without access to the domain network, your SELinux permissions are reduced causing a lack in system functionality until you rejoin the domain network and login / out. 

Version-Release number of selected component (if applicable):
1.11.4-1

How reproducible:
Always

Steps to Reproduce:
1. Join a laptop to a freeipa domain.
2. In freeipa, create a default selinux user map with a low label, ie user_u:user_r:user_t:s0. Then for the laptop system create a hbac rule for the user, and the laptop. Then create an selinux map for that hbac rule such as staff_u:staff_r:staff_t:s0:c0.c1023. Ensure that when you login to the laptop on the network, you get the staff role.
3. Disconnect all network devices on the laptop, reboot and login.

Actual results:
id -Z is user_u:user_r:user_t:s0

Expected results:
Since a login has already occured the label of staff_u:staff_r:staff_t:s0:c0.c1023 should be cached, and given to the user.

Additional info:
Given the nature of this bug, where a user may end up mislabelled, either in a higher or lower context depending on the setup of the freeipa selinux defaults, this may pose a security risk.

--- Additional comment from Jakub Hrozek on 2014-03-03 11:29:14 EST ---

Thank you for the bug report. I reproduced your problem and I'm working on a fix.
Comment 1 Jakub Hrozek 2014-03-04 15:55:47 UTC 
Upstream ticket:
https://fedorahosted.org/sssd/ticket/2264
Comment 2 Jakub Hrozek 2014-03-05 12:20:58 UTC 
Fixed upstream:
    master: 0c1a13e435ceab2038233bec3a7468c726b903b9
    sssd-1-11: 5f904508153151975e860df72b66753b129a48f4
Comment 4 Kaleem 2014-03-21 08:50:07 UTC 
Verified.

now sssd cache persistent after reboot.

[root@rhel70-client ~]# rpm -q sssd ipa-client
sssd-1.11.2-60.el7.x86_64
ipa-client-3.3.3-25.el7.x86_64
[root@rhel70-client ~]# 

Steps used for verification:
============================
On IPA Master
=============
(1) Added selinux context "staff_u" for user "tuser1" on client .

[root@master ~]# ipa hbacrule-show testrule1
  Rule name: testrule1
  Enabled: TRUE
  Users: tuser1
  Hosts: rhel70-client.testrelm.test
[root@master ~]# ipa selinuxusermap-show selinuxrule1
  Rule name: selinuxrule1
  SELinux User: staff_u:s0-s0:c0.c1023
  HBAC Rule: testrule1
  Enabled: TRUE
[root@master ~]# 

On IPA Client
=============
(2)selinuxusermap context "staff_u" is shown for user "tuser1" on client machine

[root@rhel70-client ~]# ssh -l tuser1 rhel70-client.testrelm.test id -Z
tuser1.test's password: 
staff_u:staff_r:staff_t:s0-s0:c0.c1023
Could not chdir to home directory /home/tuser1: No such file or directory
[root@rhel70-client ~]# 

(3)Rebooted client machine

[root@rhel70-client ~]# reboot
Connection to 10.65.207.134 closed by remote host.
Connection to 10.65.207.134 closed.
[ksiddiqu@ksiddiqu ~]$ 

[ksiddiqu@ksiddiqu ~]$ ssh root.207.134
reverse mapping checking getaddrinfo for dhcp207-134.lab.eng.pnq.redhat.com [10.65.207.134] failed - POSSIBLE BREAK-IN ATTEMPT!
root.207.134's password: 
Last login: Fri Mar 21 16:41:42 2014 from 10.65.193.58
[root@rhel70-client ~]# 

(4)selinuxusermap context "staff_u" is shown for user "tuser1" on client machine even after reboot.

[root@rhel70-client ~]# ssh -l tuser1 rhel70-client.testrelm.test id -Z
tuser1.test's password: 
staff_u:staff_r:staff_t:s0-s0:c0.c1023
Could not chdir to home directory /home/tuser1: No such file or directory
[root@rhel70-client ~]#
Comment 5 Ludek Smid 2014-06-13 11:01:50 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.