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.
+++ This bug was initially created as a clone of Bug #1057333 +++
Description of problem:
python-kerberos 1.1 includes an off-by-one bug, with the result that it incorrectly encodes the Kerberos username into a GSSAPI message and authentication always fails. The bug was reported and fixed upstream:
http://trac.calendarserver.org/ticket/355
Version-Release number of selected component (if applicable):
1.1
How reproducible:
Always.
Additional info:
Remove the " + 1" from the end of line 358 in python-kerberos-1.1/src/kerberosgss.c and rebuild python-kerberos. Authentication now succeeds. This is the fix to issue 355 upstream:
http://trac.calendarserver.org/ticket/355http://trac.calendarserver.org/changeset?reponame=&new=4895%40PyKerberos%2Ftrunk&old=4241%40PyKerberos%2Ftrunk
--- Additional comment from RHEL Product and Program Management on 2014-01-23 15:54:18 EST ---
Since this bug report was entered in bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
--- Additional comment from A. Jesse Jiryu Davis on 2014-01-23 15:58:49 EST ---
Discovered via this PyMongo bug report:
https://jira.mongodb.org/browse/PYTHON-626
--- Additional comment from Rob Crittenden on 2014-02-11 15:30:41 EST ---
You need a Kerberos server to test against. I tested with IPA using this:
# ipa-server-install ...
# kinit admin
# ipa service-add test/`hostname` --force
# ipa-getkeytab -s `hostname` -p test/`hostname` -k test.keytab
# export KRB5_KTNAME=`pwd`/test.keytab
# python wrap.py
Prior to the fix the response is `admin\x00' and with the fix just 'admin' where EXAMPLE.COM is your Kerberos realm.
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/RHBA-2015-0429.html