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.
Bug 2132424 - FR cannot create a TCP socket (avc: denied { name_connect } for pid comm="radiusd" dest=1813 )
Summary: FR cannot create a TCP socket (avc: denied { name_connect } for pid comm="rad...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: selinux-policy
Version: 9.1
Hardware: Unspecified
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Nikola Knazekova
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-10-05 15:52 UTC by Filip Dvorak
Modified: 2023-05-09 10:20 UTC (History)
3 users (show)

Fixed In Version: selinux-policy-34.1.44-1.el9
Doc Type: Bug Fix
Doc Text:
Cause: FR server cannot create a TCP socket because of selinux policy. Consequence: FR server cannot create a TCP connection. Fix: Allow radiusd connect to the radacct port Result: FR server can create a TCP connection
Clone Of:
Environment:
Last Closed: 2023-05-09 08:16:52 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-135757 0 None None None 2022-10-05 16:01:52 UTC
Red Hat Product Errata RHBA-2023:2483 0 None None None 2023-05-09 08:17:08 UTC

Description Filip Dvorak 2022-10-05 15:52:57 UTC
Description of problem:
FR can forward auth or acct messages to the second FR server. It uses UDP  protocol by default but in proxy.conf it is possible to configure to use TCP protocol between these servers. 
The problem is that the FR server cannot create a TCP connection because of selinux policy.
 
Version-Release number of selected component (if applicable):
RHEL-9.1.0-20221004.0
freeradius-3.0.21-34.el9.x86_64
selinux-policy-34.1.43-1.el9.noarch

How reproducible:


Steps to Reproduce:
1. dnf install freeradius freeradius-utils -y
2. configure home_server in /etc/raddb/proxy.conf
realm NULL {
}

realm redhat.com {
    pool = pool_redhat.com
    nostrip
}

home_server redhat.com {
    type = auth+acct
    ipaddr = #(random ip_addr)
    port = 1812
    secret = testing123
    status_check = none
    proto = tcp

}

home_server_pool pool_redhat.com {
    type = fail-over
    home_server = redhat.com
}

3. generate certificates for FR (/etc/raddb/certs/boostrap)
4. systemctl start radiusd
5. echo 'User-Name=localuser,Acct-Session-Id=60000061,Acct-Status-Type=Start,NAS-IP-Address=192.168.111.100,NAS-Port=0'| radclient -x localhost:1813 acct testing123 

Actual results:
radiusd log:
...
Error: Failed opening new proxy socket 'proxy (0.0.0.0, 0) -> home_server (10.0.138.199, 1813)' : Failed connecting socket: Permission denied
...

AVC message:
Enforcing mode:
time->Wed Oct  5 11:42:45 2022
type=PROCTITLE msg=audit(1664984565.302:626): proctitle=2F7573722F7362696E2F72616469757364002D64002F6574632F7261646462
type=SYSCALL msg=audit(1664984565.302:626): arch=c000003e syscall=42 success=no exit=-13 a0=5 a1=7f43c9ac79a0 a2=10 a3=7f43c9ac7a28 items=0 ppid=1 pid=12154 auid=4294967295 uid=95 gid=95 euid=95 suid=95 fsuid=95 egid=95 sgid=95 fsgid=95 tty=(none) ses=4294967295 comm="radiusd" exe="/usr/sbin/radiusd" subj=system_u:system_r:radiusd_t:s0 key=(null)
type=AVC msg=audit(1664984565.302:626): avc:  denied  { name_connect } for  pid=12154 comm="radiusd" dest=1813 scontext=system_u:system_r:radiusd_t:s0 tcontext=system_u:object_r:radacct_port_t:s0 tclass=tcp_socket permissive=0

Permissive mode:
time->Wed Oct  5 11:45:47 2022
type=PROCTITLE msg=audit(1664984747.108:630): proctitle=2F7573722F7362696E2F72616469757364002D64002F6574632F7261646462
type=SYSCALL msg=audit(1664984747.108:630): arch=c000003e syscall=42 success=no exit=-113 a0=5 a1=7f60ed1d19a0 a2=10 a3=7f60ed1d1a28 items=0 ppid=1 pid=12175 auid=4294967295 uid=95 gid=95 euid=95 suid=95 fsuid=95 egid=95 sgid=95 fsgid=95 tty=(none) ses=4294967295 comm="radiusd" exe="/usr/sbin/radiusd" subj=system_u:system_r:radiusd_t:s0 key=(null)
type=AVC msg=audit(1664984747.108:630): avc:  denied  { name_connect } for  pid=12175 comm="radiusd" dest=1813 scontext=system_u:system_r:radiusd_t:s0 tcontext=system_u:object_r:radacct_port_t:s0 tclass=tcp_socket permissive=1


Expected results:
The FR should forward acct or auth messages to the home_server (ip_addr in a proxy.conf) via TCP

Additional info:
It is possible to use TCMS tests -> BZ#610496  /CoreOS/freeradius/Multihost/copy-acct-to-home-server-sanity [freeradius:3.0]

Comment 15 errata-xmlrpc 2023-05-09 08:16:52 UTC
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 (selinux-policy bug fix and enhancement update), 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-2023:2483


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