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 1084068 - ipv6 address handling in krb5.conf
Summary: ipv6 address handling in krb5.conf
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: krb5
Version: 7.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Nalin Dahyabhai
QA Contact: Patrik Kis
URL:
Whiteboard:
Depends On:
Blocks: 1083244 1113520
TreeView+ depends on / blocked
 
Reported: 2014-04-03 14:29 UTC by Guenther Deschner
Modified: 2015-03-05 10:00 UTC (History)
8 users (show)

Fixed In Version: krb5-1.12.2-7.el7
Doc Type: Bug Fix
Doc Text:
Cause: When attempting to look up the addresses of servers configured in /etc/krb5.conf, the Kerberos client library did not recognize some of the result codes which could be returned by the resolver libraries. Consequence: Instead of treating the inability to parse an IPv6 address as an IPv4 address as a non-fatal error, the client library would treat it as a fatal error, and fail to contact the server. Fix: Patches were added to help ensure that these specific result codes could be interpreted properly. Result: These errors no longer occur.
Clone Of:
Environment:
Last Closed: 2015-03-05 10:00:44 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1109102 0 medium CLOSED Kerberos does not handle incorrect Active Directory DNS SRV entries correctly 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHSA-2015:0439 0 normal SHIPPED_LIVE Moderate: krb5 security, bug fix and enhancement update 2015-03-05 14:38:14 UTC

Description Guenther Deschner 2014-04-03 14:29:03 UTC
Description of problem:

libkrb5 seems to have problems dealing with setups where a KDC has a ipv4 and a ipv6 addresses and when both addresses are put into a krb5.conf file.

When the KDC cannot be connected using the ipv6 address, kinit will only retry with the ipv4 address when the ipv6 address has the portnummer attached to it.

With this kinit will fail with "kinit: Invalid argument while getting initial credentials"

[realms]
        AD.TEST.COM = {
                kdc = [1234:52:0:2223::1:1]
                kdc = 12.34.56.78
        }

while the ipv4 address is tried with this configuration (and kinit succeeds).

[realms]
        AD.TEST.COM = {
                kdc = [1234:52:0:2223::1:1]:88
                kdc = 12.34.56.78
        }


Version-Release number of selected component (if applicable):
krb5-libs-1.11.3-49.el7

Comment 11 errata-xmlrpc 2015-03-05 10:00:44 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, 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://rhn.redhat.com/errata/RHSA-2015-0439.html


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