Description of problem: ANC denial prevents freeradius2 communicate with postgresql on RHEL5, while on RHEL6 it is working out of the box. Version-Release number of selected component (if applicable): # rpm -q freeradius2 postgresql selinux-policy freeradius2-2.1.12-3.el5 postgresql-8.1.23-1.el5_7.3 selinux-policy-2.4.6-327.el5 How reproducible: always Steps to Reproduce: 1. run test /CoreOS/freeradius/Sanity/postgresql-auth-test 2. When radiusd start the following AVC appears and the test fails: type=AVC msg=audit(1340196443.406:1177): avc: denied { name_connect } for pid=22893 comm="radiusd" dest=5432 scontext=root:system_r:radiusd_t:s0 tcontext=system_u:object_r:postgresql_port_t:s0 tclass=tcp_socket Actual results: AVC denial Expected results: no AVC denial Additional info: It seems there are missing policies on RHEL5. This test was newer launched on RHEL5; it was only now made ready for RHEL5 that's the reason why this error was hidden so far. [root@rhel58 ~]# sesearch -A -C -s radiusd_t -t ldap_port_t -c tcp_socket Found 1 av rules: allow radiusd_t ldap_port_t : tcp_socket { recv_msg send_msg name_connect }; [root@rhel63 ~]# sesearch -A -C -s radiusd_t -t ldap_port_t -c tcp_socket Found 5 semantic av rules: allow radiusd_t ldap_port_t : tcp_socket { recv_msg send_msg name_connect } ; allow radiusd_t port_type : tcp_socket { recv_msg send_msg } ; DT allow radiusd_t reserved_port_type : tcp_socket name_connect ; [ allow_ypbind ] DT allow radiusd_t rpc_port_type : tcp_socket name_bind ; [ allow_ypbind ] DT allow radiusd_t port_type : tcp_socket { recv_msg send_msg } ; [ allow_ypbind ]
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.
It needs to be backported from RHEL6.
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-0060.html