Description of problem: AVC denial while fetching file through squid with kerberos authentication How reproducible: Always Steps to Reproduce: 1. Setup squid with kerberos authentication 2. Use curl to access some internet site Actual results: time->Tue Apr 16 08:11:44 2013 type=SYSCALL msg=audit(1366114304.233:42): arch=c000003e syscall=42 success=no exit=-13 a0=19 a1=1fd9a614 a2=10 a3=0 items=0 ppid=11987 pid=11989 auid=4294967295 uid=23 gid=23 euid=23 suid=0 fsuid=23 egid=23 sgid=23 fsgid=23 tty=(none) ses=4294967295 comm="squid" exe="/usr/sbin/squid" subj=root:system_r:squid_t:s0 key=(null) type=AVC msg=audit(1366114304.233:42): avc: denied { name_connect } for pid=11989 comm="squid" dest=113 scontext=root:system_r:squid_t:s0 tcontext=system_u:object_r:auth_port_t:s0 tclass=tcp_socket ---- time->Tue Apr 16 08:11:44 2013 type=SYSCALL msg=audit(1366114304.647:43): arch=c000003e syscall=42 success=no exit=-13 a0=19 a1=1fd9a614 a2=10 a3=1fd9dc90 items=0 ppid=11987 pid=11989 auid=4294967295 uid=23 gid=23 euid=23 suid=0 fsuid=23 egid=23 sgid=23 fsgid=23 tty=(none) ses=4294967295 comm="squid" exe="/usr/sbin/squid" subj=root:system_r:squid_t:s0 key=(null) type=AVC msg=audit(1366114304.647:43): avc: denied { name_connect } for pid=11989 comm="squid" dest=113 scontext=root:system_r:squid_t:s0 tcontext=system_u:object_r:auth_port_t:s0 tclass=tcp_socket Expected results: No AVC denials
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release.
We allow it in Fedora/RHEL6. #============= squid_t ============== #!!!! This avc is allowed in the current policy allow squid_t auth_port_t:tcp_socket name_connect;
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-2013-1312.html