Bug 747321
Summary: | SELinux is preventing /usr/sbin/sshd from getattr operation on /root/.hushlogin file | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Milos Malik <mmalik> |
Component: | selinux-policy | Assignee: | Miroslav Grepl <mgrepl> |
Status: | CLOSED ERRATA | QA Contact: | Milos Malik <mmalik> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.2 | CC: | dwalsh, jrieden, syeghiay |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | selinux-policy-3.7.19-119.el6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-12-06 10:20:21 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Milos Malik
2011-10-19 13:44:34 UTC
Are you able to log in? Yes, I'm able to log in. I suspect that more services (not just login and sshd) will read this file. Really read? What are you getting in permissive mode? You're right. getattr is enough. Here is what I see in permissive mode: ---- time->Wed Oct 19 09:58:36 2011 type=SYSCALL msg=audit(1319032716.579:84457): arch=40000003 syscall=195 success=yes exit=0 a0=bfd301fc a1=bfd3019c a2=941ff4 a3=bfd301fc items=0 ppid=27477 pid=27481 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts1 ses=55 comm="sshd" exe="/usr/sbin/sshd" subj=unconfined_u:system_r:sshd_t:s0-s0:c0.c1023 key=(null) type=AVC msg=audit(1319032716.579:84457): avc: denied { getattr } for pid=27481 comm="sshd" path="/root/.hushlogin" dev=dm-0 ino=131098 scontext=unconfined_u:system_r:sshd_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:local_login_home_t:s0 tclass=file ---- Lets add this to the auth_use_pam() Fixed in selinux-policy-3.7.19-119.el6.noarch 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-2011-1511.html |