Red Hat Bugzilla – Bug 1405716
SELinux is preventing /usr/bin/python2.7 from read access on the file unix.
Last modified: 2018-04-10 08:26:24 EDT
SELinux is preventing /usr/bin/python2.7 from read access on the file unix. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that python2.7 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: # ausearch -c 'ipa-dnskeysyncd' --raw | audit2allow -M my-ipadnskeysyncd # semodule -i my-ipadnskeysyncd.pp Additional Information: Source Context system_u:system_r:ipa_dnskey_t:s0 Target Context system_u:object_r:proc_net_t:s0 Target Objects unix [ file ] Source ipa-dnskeysyncd Source Path /usr/bin/python2.7 Port <Unknown> Host server.interlinx.bc.ca Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-102.el7_3.7.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-514.2.2.el7.x86_64 #1 SMP Tue Dec 6 23:06:41 UTC 2016 x86_64 x86_64 Alert Count 825 First Seen 2016-12-16 22:09:54 EST Last Seen 2016-12-17 13:23:10 EST Local ID 06ab36fb-2d79-4937-a7ca-51c50af854cf Raw Audit Messages type=AVC msg=audit(1481998990.686:7332): avc: denied { read } for pid=29769 comm="ipa-dnskeysyncd" name="unix" dev="proc" ino=4026532003 scontext=system_u:system_r:ipa_dnskey_t:s0 tcontext=system_u:object_r:proc_net_t:s0 tclass=file Hash: ipa-dnskeysyncd,ipa_dnskey_t,proc_net_t,file,read
# ls -il /proc/net/unix 4026532003 -r--r--r--. 1 root root 0 Dec 19 05:28 /proc/net/unix # ls -Z /proc/net/unix -r--r--r--. root root system_u:object_r:proc_net_t:s0 /proc/net/unix # My guess is that SELinux policy developers should allow { getattr open read } to proc_net_t for all domains.
https://github.com/fedora-selinux/selinux-policy-contrib/pull/36
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. https://access.redhat.com/errata/RHBA-2018:0763