#2047 sssd_be crashes when referrals enabled
Closed: Duplicate None Opened 10 years ago by mkosek.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 6): Bug 994526

Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.

Description of problem: SSSD crashes when referrals are enabled on the client.
In this particular case, there are 3 different domain and referrals are
enabled.

Version-Release number of selected component (if applicable):
sssd-1.9.2-82.el6.x86_64

How reproducible: Customer hits this often (during login) and when referrals
enabled.

Steps to Reproduce:
1. Configure SSSD to use ldap provider
2. Enable referrals.
3.

Actual results: sssd_be crashes frequently.


Expected results: No crashes.


Additional info: Seems to be related to
https://bugzilla.redhat.com/show_bug.cgi?id=986824 (crash reported against
sssd_pam).

needs backport to 1.9 for RHEL6

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
milestone: NEEDS_TRIAGE => SSSD 1.10.2
review: True => 0
selected: =>
testsupdated: => 0

I suspect this will be the same as the pam responder crash.

owner: somebody => jhrozek
status: new => assigned

Dupe of #1869

resolution: => duplicate
status: assigned => closed

Sorry the previous comment was probably too brief. I analyzed the core file and worked with the reporter of the original Red Hat bugzilla. The problem was caused by an access-after-free after the PAM responder timed out as well. I also made sure that a test package with a fix for #1869 made the problem disappear.

Metadata Update from @mkosek:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.10.2

7 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/3089

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata