Bug 748895

Summary: Only access sssd_nss internal hash table if it was initialized
Product: Red Hat Enterprise Linux 5 Reporter: Jakub Hrozek <jhrozek>
Component: sssdAssignee: Stephen Gallagher <sgallagh>
Status: CLOSED ERRATA QA Contact: IDM QE LIST <seceng-idm-qe-list>
Severity: unspecified Docs Contact:
Priority: high    
Version: 5.8CC: dpal, grajaiya, jgalipea, kbanerje, prc, syeghiay
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: sssd-1.5.1-38.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 746037 Environment:
Last Closed: 2012-02-21 06:26:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 746037    
Bug Blocks:    

Comment 1 Jakub Hrozek 2011-10-25 15:32:51 UTC
Upstream ticket:
https://fedorahosted.org/sssd/ticket/1058

Comment 2 Kaushik Banerjee 2011-12-30 19:37:03 UTC
Verified that sssd_nss does not crash and no coredump is created on following the steps to reproduce as in the original comment.

Verified in version:
# rpm -qi sssd | head
Name        : sssd                         Relocations: (not relocatable)
Version     : 1.5.1                             Vendor: Red Hat, Inc.
Release     : 47.el5                        Build Date: Tue 13 Dec 2011 08:49:14 AM EST
Install Date: Wed 28 Dec 2011 02:47:40 AM EST      Build Host: x86-002.build.bos.redhat.com
Group       : Applications/System           Source RPM: sssd-1.5.1-47.el5.src.rpm
Size        : 3651336                          License: GPLv3+
Signature   : DSA/SHA1, Wed 14 Dec 2011 12:17:11 PM EST, Key ID fd372689897da07a
Packager    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
URL         : http://fedorahosted.org/sssd/
Summary     : System Security Services Daemon

Comment 3 errata-xmlrpc 2012-02-21 06:26:26 UTC
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.

http://rhn.redhat.com/errata/RHBA-2012-0164.html