Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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:

radclient does not detect 4. level and higher domain name as a domain name and it interprets it as an ipv4 address. It seems to me, there is some kind of issue with domain name/ipv4 address detection in radclient code, because of dots.

It is a regression. Older version works fine.


Version-Release number of selected component (if applicable):

freeradius-3.0.12-1.el7_3


How reproducible:

100%


Steps to Reproduce:

1. We test domain blabla.redhat.com, which does not exist. radclient works fine.

# radtest krbuser krbpassword blabla.redhat.com 0 testing123
radclient: Failed resolving "blabla.redhat.com" to IPv4 address: Name or service not known

2. Then we test domain blabla.blabla.redhat.com, which also does not exist. radclient does not work fine.

# radtest krbuser krbpassword blabla.blabla.redhat.com 0 testing123
radclient: Invalid IPv4 address string "blabla.blabla.redhat.com"


Actual results:

radclient does not detect domain name and it thinks it got ipv4 address.


Expected results:

radclient correctly detects domain name.

This is a logic bug in fr_pton4(). It assumes that if a non-zero inlen argument is supplied, then the value string is an IP address, which doesn't have to be and is not true in this case. A fix is in order.

Pull request submitted upstream: https://github.com/FreeRADIUS/freeradius-server/pull/1919

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