#2658 memory leak in sysdb_search_custom
Closed: Fixed Opened by jhrozek.

Pavel Reichl fixed a memory leak in a sysdb function a while ago. I'm filing this ticket for bookkeeping.

Fixed in:
- a4caef931a245fb3c44b70ea65a58bd0c1ff8dc4
- 09579ae252c181c7884defc0612c36108f6cf509
- af63cdbfe0c917e0dc921232f67295fdc48d1e32


Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.12.0
owner: somebody => preichl

Fields changed

resolution: => fixed
status: new => closed

Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1192362 (Red Hat Enterprise Linux 6)

rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=1192362 1192362]

Metadata Update from @jhrozek:
- Issue assigned to preichl
- Issue set to the milestone: SSSD 1.12.0

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

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