Bug 729068

Summary: kadmin incompatible with kdc
Product: Red Hat Enterprise Linux 6 Reporter: Jarrod Makin <jarrod.makin>
Component: krb5Assignee: Nalin Dahyabhai <nalin>
Status: CLOSED ERRATA QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1CC: dpal, jplans, prc
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: krb5-1.9-11.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 17:37:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jarrod Makin 2011-08-08 16:28:43 UTC
Description of problem:

I have an RHEL4 box as my KDC and an RHEL6.1 server attempting to connect.

[root@rhel6box ~]# kadmin -p user/admin
Authenticating as principal user/admin with password.
Password for user/admin.UK:
kadmin: GSS-API (or Kerberos) error while initializing kadmin interface

on the RHEL4 box, the following is logged in /var/log/kadmind.log

... kadmind[31449](Notice): Authentication attempt failed: 10.0.1.4, GSS-API error strings are:
... kadmind[31449](Notice): Authentication attempt failed: 10.0.1.4, GSS-API error strings are:
... kadmind[31449](Notice):     Incorrect channel bindings were supplied
... kadmind[31449](Notice):     Incorrect channel bindings were supplied
... kadmind[31449](Notice):     No error
... kadmind[31449](Notice):     No error
... kadmind[31449](Notice):    GSS-API error strings complete.
... kadmind[31449](Notice):    GSS-API error strings complete.


rpms installed are:
krb5-libs-1.9-9.el6_1.1.x86_64
krb5-workstation-1.9-9.el6_1.1.x86_64

my current workaround is to downgrade to
krb5-libs-1.8.2-3.el6_0.7.x86_64
krb5-workstation-1.8.2-3.el6_0.7.x86_64

Comment 6 errata-xmlrpc 2011-12-06 17:37:08 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.

http://rhn.redhat.com/errata/RHBA-2011-1707.html