SSSD / sssd

#643 Don't pass NULL to printf for TLS errors
Closed: Fixed Opened by sejeff.

Closed: Fixed
Reopen Issue

SEJeff: thanks for catching this. Can you file a bug for the 'LDAP connection error: (null)'. It is safe to pass NULL to printf in glibc but might not be so in other libcs.

The way I caused this was by futzing the sssd.conf and pointing ldap_uri to hosts that don't run ldap. After restarting sssd (which came up in offline mode), I tried to change the password. It printed these errors:

<27> Oct 12 07:48:45.000 ops2.dev1.int sssd[be[LDAP]]: Could not start TLS. (null)
<27> Oct 12 07:48:45.000 ops2.dev1.int sssd[be[LDAP]]: Could not start TLS. (null)
<27> Oct 12 07:48:45.000 ops2.dev1.int sssd[be[LDAP]]: Could not start TLS. (null)

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.6.0

Fields changed

coverity: =>
owner: somebody => jhrozek
upgrade: => 0

Fixed in 4a28fb10122bd74ba33607af46f028813de9161d

resolution: => fixed
status: new => closed

Backported to sssd-1-5

b6ed1d6569fea94cb58d91877c1873ec28328fd7

milestone: SSSD 1.6.0 => SSSD 1.5.9
patch: => 0
rhbz: =>

Fields changed

rhbz: => 0

Metadata Update from @sejeff:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.5.9

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/1685

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.
Metadata
None
None
None
High
defect
SSSD
1.2.4
None
0
0
0
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.