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.
When SSSD communicated with an OpenLDAP server, which supported server-side password policies but did not list them in the "supportedControl" attribute of the server's rootDSE entry, SSSD terminated unexpectedly with a segmentation fault. This was a regression introduced in version 1.5.1-34.el6 of the sssd package. An upstream patch has been provided to fix this bug.
DescriptionStephen Gallagher
2011-06-16 22:07:07 UTC
How to reproduce:
To reproduce the segfault it should be sufficient to add
objectClass: pwdPolicy
pwdAttribute: userPassword
to a user entry and try to log in with this user.
For completeness, to use the ppolicy overlay please add:
olcModuleLoad: ppolicy.la
olcPPolicyDefault: cn=pwdconfig,ou=config,dc=your,dc=base,dc=dn
olcOverlay: ppolicy
to /etc/openldap/slapd.d/cn=config/olcDatabase={1}bdb.ldif .
Create a policy like
dn: cn=pwdconfig,ou=config,dc=your,dc=base,dc=dn
objectClass: pwdPolicy
objectClass: top
objectClass: person
pwdAttribute: userPassword
sn: Password Policy
cn: pwdconfig
pwdMaxAge: 100
pwdExpireWarning: 10
pwdGraceAuthNLimit: 3
and add
objectClass: pwdPolicy
pwdAttribute: userPassword
pwdPolicySubentry: cn=pwdconfig,ou=config,dc=your,dc=base,dc=dn
to a user object.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
When SSSD communicated with an OpenLDAP server, which supported server-side password policies but did not list them in the "supportedControl" attribute of the server's rootDSE entry, SSSD terminated unexpectedly with a segmentation fault. This was a regression introduced in version 1.5.1-34.el6 of the sssd package. An upstream patch has been provided to fix this bug.
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-2011-1529.html
How to reproduce: To reproduce the segfault it should be sufficient to add objectClass: pwdPolicy pwdAttribute: userPassword to a user entry and try to log in with this user. For completeness, to use the ppolicy overlay please add: olcModuleLoad: ppolicy.la olcPPolicyDefault: cn=pwdconfig,ou=config,dc=your,dc=base,dc=dn olcOverlay: ppolicy to /etc/openldap/slapd.d/cn=config/olcDatabase={1}bdb.ldif . Create a policy like dn: cn=pwdconfig,ou=config,dc=your,dc=base,dc=dn objectClass: pwdPolicy objectClass: top objectClass: person pwdAttribute: userPassword sn: Password Policy cn: pwdconfig pwdMaxAge: 100 pwdExpireWarning: 10 pwdGraceAuthNLimit: 3 and add objectClass: pwdPolicy pwdAttribute: userPassword pwdPolicySubentry: cn=pwdconfig,ou=config,dc=your,dc=base,dc=dn to a user object.