Bug 1386776

Summary:	Does not properly create home directory when I login through ssh using SSSD or Winbind Active Directory Authentication
Product:	Red Hat Enterprise Linux 7	Reporter:	Jordi Rubalcaba <jordi.rubalcaba>
Component:	selinux-policy	Assignee:	Lukas Vrabec <lvrabec>
Status:	CLOSED WONTFIX	QA Contact:	Milos Malik <mmalik>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	dapospis, jordi.rubalcaba, lvrabec, mgrepl, mmalik, pkis, plautrba, pvrabec, ssekidde, tmraz, zpytela
Target Milestone:	rc	Flags:	lvrabec: needinfo? (jordi.rubalcaba)
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-28 19:14:30 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Jordi Rubalcaba 2016-10-19 15:33:32 UTC

Description of problem:

[+] Description of problem: - Applied to SSSD or Winbind Active Directory Authentication... When using pam_mkhomedir.so within the PAM stack to create home directories for users when they log in if they do not yet have a home directory, SELinux will deny SSHD from accessing /usr/sbin/mkhomedir_helper to create the directory.

[+] Version-Release number of selected component (if applicable): - selinux-policy-3.13.1-60.el7_2.7.noarch [+] How reproducible: - Always

[+] Steps to Reproduce:
1. Configure a system as a domain client of a domain server (https://access.redhat.com/solutions/1755013)
2. Verify pam_mkhomedir.so (not pam_oddjob_mkhomedir.so) is being used as the module in /etc/pam.d/password-auth.
3. SSH into the system as a domain user.

Replicated in Production Environment:
Creating home directory for adm.rubalcj. Last login: Thu Aug 25 14:01:55 2016 from [root@el7sssdclient Could not chdir to home directory /home/DOMAIN/adm.rubalcj: Permission denied

-bash: /home/DOMAIN/adm.rubalcj/.bash_profile: Permission denied

[root@RHEL7-Server~]# ls -la /home/DOMAIN/
total 0
drwxrwxr-x. 5 root root 60 Aug 25 14:12 .
drwxr-xr-x. 3 root root 19 Aug 24 07:14 ..
drwx--x--x. 3 user1 domain users 74 Aug 24 08:36 user1d---------. 3
adm.rubalcj domain users 74 Aug 25 14:12 adm.rubalcj

Version-Release number of selected component (if applicable):
selinux-policy-3.13.1-60.el7_2.7.noarch

How reproducible:
Always

Steps to Reproduce:
1. Configure a system as a domain client of a domain server (https://access.redhat.com/solutions/1755013)
2. Verify pam_mkhomedir.so (not pam_oddjob_mkhomedir.so) is being used as the module in /etc/pam.d/password-auth.
3. SSH into the system as a domain user.

Actual results:
[+] Actual results: [root@el7sssdclient DOMAIN]# ssh administrator@localhost administrator@localhost's password: Creating directory '/home/administrator'. Unable to create and initialize directory '/home/administrator'. Last login: Wed Aug 24 16:50:05 2016 from localhost Could not chdir to home directory /home/administrator: No such file or directory -bash-4.2$

Expected results:
[+] Expected results: [root@el7sssdclient home]# ssh administrator@localhost administrator@localhost's password: Creating directory '/home/administrator'. Last login: Wed Aug 24 16:50:27 2016 from localhost [administrator@el7sssdclient ~]$

Additional info:
Setting setenforce to 0 works around this issue temporarily.

Suggestion from Red Hat Support:
Jordi, It's difficult to say exactly when a package will be pushed to the stable repository for customer consumption. However, the patched version of the fix can be found in selinux-policy-3.13.1-96.el7, so when this or a later version of selinux-policy is pushed out, you should see the fix.

Striker

Comment 4 Lukas Vrabec 2018-06-11 08:52:42 UTC

Hi, 

Are you able to reproduce it?

If yes, please reproduce it and attach output of:
# ausearch -m AVC -ts recent 

Thanks,
Lukas.

Comment 6 Zdenek Pytela 2019-02-28 19:14:30 UTC

This issue was not selected to be included in Red Hat Enterprise Linux 7.7 because it is seen either as low or moderate impact to a small number of use-cases. The next release will be in Maintenance Support 1 Phase, which means that qualified Critical and Important Security errata advisories (RHSAs) and Urgent Priority Bug Fix errata advisories (RHBAs) may be released as they become available.

We will now close this issue, but if you believe that it qualifies for the Maintenance Support 1 Phase, please re-open; otherwise, we recommend moving the request to Red Hat Enterprise Linux 8 if applicable.