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.

Description of problem:
Same bug of FreeRADIUS 2.2.6 in RedHat el 6.

https://bugzilla.redhat.com/show_bug.cgi?id=1248484

This bug report seems to be not correct.
It mentions FreeRADIUS 2.2.6 but it is filed against RHEL-7. Note that RHEL-7 contains FreeRADIUS version 3 and AFAIK this issue is not present there.

IMHO this issue is not relevant for the currently shipped freeradius in RHEL-7 which is: freeradius-3.0.4

According to changelogs here http://freeradius.org/press/index.html#3.0.11
freeradius v3 TLS-1.2 support was added in version 3.0.5 and the issue reported here is fixed again in version 3.0.10.

This should be fixed in 3.0.12.

I think we should close this as NOTABUG (since the problem didn't exist in 3.0.4), once we verified this is not a problem in 3.0.12 either.

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/RHEA-2017:1954