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 #1066000 +++

Upstream recently got a few patches to fix a SPNEGO iussue:
http://krbdev.mit.edu/rt/Ticket/Display.html?id=7858

This issue causes failures as reported, for exaemple here:
http://bugs.centos.org/view.php?id=6526

Without these patches BIND cannot properly reply to GSS-TSIG requests sent by Windows Clients causing them to fail to perform a signed updayte at all.

This is causing issues to people that have to rebuild BIND to use the internal SPENGO implementation.

These fixes have been indepndently tested on both Fedora 19 and Fedora 20 by two people with a custom build of krb5 libraries (F20 + the patch in the MIT report) and the original BIND packages.

Hi Nalin,

It seems to me that to reproduce this issue requires a quite lot of setup + MS Windows; or is there a simpler way?
But I've noticed that the patch carries also an upstream test modification. Do you think it is suitable to use it to verify this issue?

(In reply to Patrik Kis from comment #5)
> Hi Nalin,
> 
> It seems to me that to reproduce this issue requires a quite lot of setup +
> MS Windows; or is there a simpler way?

In out-of-band conversations with Simo, I gather that there isn't.

> But I've noticed that the patch carries also an upstream test modification.
> Do you think it is suitable to use it to verify this issue?

I was hoping it wouldn't be the sole option, but yes, that test attempts to catch the problems that we're adding fixes for.

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.