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.

A couple of memleaks and interoperability issues were recently fixed upstream that affect spnego (and therefore HTTP Negotiate) code.

Please backport the following commits:

Interop issue:
- 13fd26e1863c79f616653f6a10a58c01f65fceff
    Avoid malloc(0) in SPNEGO get_input_token

- 37af638b742dbd642eb70092e4f7781c3f69d86d
    Fix SPNEGO one-hop interop against old IIS

Memleaks:
- 1cda48a7ed4069cfc052f974ec3d76a9137c8c5a
    Fix memory leak in SPNEGO initiator 

- decccbcb5075f8fbc28a535a9b337afc84a15dee
    Fix GSS krb5 acceptor acquire_cred error handling

Check for presence will suffice

I'd like to add https://github.com/krb5/krb5/commit/c452644d91d57d8b05ef396a029e34d0c7a48920 to this list, if that's still an option.  From out-of-band conversations, I'm given to understand that the freeradius package uses the function that it fixes.

(In reply to Nalin Dahyabhai from comment #4)
> I'd like to add
> https://github.com/krb5/krb5/commit/c452644d91d57d8b05ef396a029e34d0c7a48920
> to this list, if that's still an option.  From out-of-band conversations,
> I'm given to understand that the freeradius package uses the function that
> it fixes.

Never mind this bit; we now have bug #1044739 to track it.

I would like to add this to the list:
https://github.com/krb5/krb5/commit/d160bc733a3dbeb6d84f4e175234ff18738d9f66

It is not really amemleak, but it is yet another issue I fixed in the spnego code after I spent 2 hours diagnosing a problem that would have been obvious if spnego actually did report mechanism errors.

I can open a separate bug if that's better.

(In reply to Simo Sorce from comment #6)
> I would like to add this to the list:
> https://github.com/krb5/krb5/commit/d160bc733a3dbeb6d84f4e175234ff18738d9f66

Okay, I think we'll add that to the set.

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.