SSSD / sssd

#790 Perform extra checks before attempting to close our socket after a fork
Closed: Fixed Opened by simo.

Closed: Fixed
Reopen Issue

See https://bugzilla.redhat.com/show_bug.cgi?id=670511 for an example application that does strange stuff and may cause us to close the wrong file descriptor.

Add extra code to be sure we are going to close only our own socket after a fork.

Fields changed

status: new => assigned

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.5.2

Fixed by b005a24b17fa073939baa0efe6137cb7c4f3217d

resolution: => fixed
status: assigned => closed

Fields changed

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

Metadata Update from @simo:
- Issue assigned to simo
- Issue set to the milestone: SSSD 1.5.2

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

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
Normal
defect
SSSD
1.5.0
0
https://bugzilla.redhat.com/show_bug.cgi?id=670511
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.