Bug 1389261 - SELinux is preventing /usr/bin/sss_ssh_knownhostsproxy from read access on the file unix.
Summary: SELinux is preventing /usr/bin/sss_ssh_knownhostsproxy from read access on th...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: selinux-policy
Version: 7.2
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Lukas Vrabec
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks: 1393066
TreeView+ depends on / blocked
 
Reported: 2016-10-27 10:02 UTC by Brian J. Murrell
Modified: 2017-10-12 12:21 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-12 12:19:59 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Brian J. Murrell 2016-10-27 10:02:41 UTC
SELinux is preventing /usr/bin/sss_ssh_knownhostsproxy from read access on the file unix.

*****  Plugin catchall (100. confidence) suggests   **************************

If you believe that sss_ssh_knownhostsproxy should be allowed read access on the unix file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# grep sss_ssh_knownho /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp


Additional Information:
Source Context                system_u:system_r:fail2ban_t:s0
Target Context                system_u:object_r:proc_net_t:s0
Target Objects                unix [ file ]
Source                        sss_ssh_knownho
Source Path                   /usr/bin/sss_ssh_knownhostsproxy
Port                          <Unknown>
Host                          server.interlinx.bc.ca
Source RPM Packages           whois-5.1.1-2.el7.x86_64
Target RPM Packages
Policy RPM                    selinux-policy-3.13.1-60.el7_2.9.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     server.interlinx.bc.ca
Platform                      Linux server.interlinx.bc.ca
                              3.10.0-327.36.1.el7.x86_64 #1 SMP Sun Sep 18
                              13:04:29 UTC 2016 x86_64 x86_64
Alert Count                   1206
First Seen                    2016-10-26 19:26:30 EDT
Last Seen                     2016-10-27 05:56:58 EDT
Local ID                      57e2bd68-84e0-482a-abb0-59e60c1d208b

Raw Audit Messages
type=AVC msg=audit(1477562218.699:55500): avc:  denied  { read } for  pid=21562 comm="whois" name="unix" dev="proc" ino=4026532002 scontext=system_u:system_r:fail2ban_t:s0 tcontext=system_u:object_r:proc_net_t:s0 tclass=file


type=SYSCALL msg=audit(1477562218.699:55500): arch=x86_64 syscall=access success=no exit=EACCES a0=7ffe39304c50 a1=4 a2=7ffe39304c5e a3=3 items=0 ppid=21561 pid=21562 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=whois exe=/usr/bin/whois.md subj=system_u:system_r:fail2ban_t:s0 key=(null)

Hash: sss_ssh_knownho,fail2ban_t,proc_net_t,file,read

Comment 2 Brian J. Murrell 2016-11-07 14:07:14 UTC
Here's an additional AVC getting caught up:

type=AVC msg=audit(1478527518.341:55611): avc:  denied  { read } for  pid=8559 comm="sss_ssh_knownho" name="unix" dev="proc" ino=4026532002 scontext=system_u:system_r:fail2ban_t:s0 tcontext=system_u:object_r:proc_net_t:s0 tclass=file

The context (NPI) here is that fail2ban can call both whois as well as an ssh command to execute a command on a remote machine.  This is an IPA environment, hence the /usr/bin/sss_ssh_knownhostsproxy.

Comment 6 Lukas Vrabec 2017-10-12 12:19:59 UTC
We're going to close this bug as WONTFIX because

 * of limited capacity of selinux-policy developers
 * the bug is related to EPEL component or 3rd party SW only
 * the bug appears in unsupported configuration 

We believe this bug can be fixed via a local policy module.
For more information please see: 

 * https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/selinux_users_and_administrators_guide/sect-security-enhanced_linux-troubleshooting-fixing_problems#sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow

If you disagree, please re-open the bug.

Comment 7 Lukas Vrabec 2017-10-12 12:21:45 UTC
We're going to close this bug as WONTFIX because

 * of limited capacity of selinux-policy developers
 * the bug is related to EPEL component or 3rd party SW only
 * the bug appears in unsupported configuration 

We believe this bug can be fixed via a local policy module.
For more information please see: 

 * https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/selinux_users_and_administrators_guide/sect-security-enhanced_linux-troubleshooting-fixing_problems#sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow

If you disagree, please re-open the bug.


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