Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionBrian 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
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.
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