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

rlm_krb5 will corrupt memory or seg fault due to improperly passed pointer to memcpy.

rlm_krb5 will also seg fault due a bug in the krb5 function krb5_copy_context(), this problem and it's solution is described in Bug #1044735.

A discussion concerning the problems with rlm_krb5 can be found here:

http://freeradius.1045715.n5.nabble.com/received-signal-SIGSEGV-Segmentation-fault-malloc-consolidate-av-0x7ffff5e2de80-at-malloc-c-5196-td5723967.html

Attached is a patch which brings all the rlm_krb5 files up to date with the current version of these files in the upstream FreeRADIUS git repo (branch v3.0.x), this will become the basis for the next FreeRADIUS 3.x release.

--- Additional comment from John Dennis on 2013-12-18 17:07:42 EST ---

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.