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

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 b005a24

resolution: => fixed
status: assigned => closed

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

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

Login to comment on this ticket.

Metadata