#1288 Invalid keytab path logged when using the default keytab
Closed: Fixed None Opened 8 years ago by myllynen.

In case of principal error when using the default keytab with GSSAPI the keytab path is printed as (null) which is confusing:

Apr 3 11:59:20 testhost [sssd[ldap_child[10802]]]: Failed to initialize credentials using keytab [(null)]: Client 'host/testhost@TEST.REALM' not found in Kerberos database. Unable to create GSSAPI-encrypted LDAP connection.

Thank you. It's not only confusing but potentially dangerous, because with other libc implementations, printing a NULL string might cause a crash.

I've noticed some other occurrences of printing NULL lately and I'll roll them all into a single patch.

Actually, I've already got a patch ready for this. Sent to the list for review.

owner: somebody => sgallagh
patch: 0 => 1
priority: minor => trivial
status: new => assigned

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.9.0

Fixed by:
- c87a579 (master)
- d402f62 (sssd-1-8)

component: SSSD => LDAP Provider
milestone: SSSD 1.9.0 => SSSD 1.8.2 (LTM)
resolution: => fixed
status: assigned => closed

Metadata Update from @myllynen:
- Issue assigned to sgallagh
- Issue set to the milestone: SSSD 1.8.2 (LTM)

3 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/2330

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.