#2468 Don't set the umask in the utility function that creates sockets
Closed: Fixed None Opened 6 years ago by jhrozek.

SSSD would create the sockets that responders talk to using a custom umask and then set the sssd-wide secure umask. It's not very convenient and discoverable that a utility function sets the sssd-wide umask. Some global setup function, like server_setup() might be a better fit.


Fields changed

owner: somebody => mzidek

Fields changed

owner: mzidek => preichl

This is a cleanup after the first round of patches for #2370 landed. Moving to 1.12.3

milestone: NEEDS_TRIAGE => SSSD 1.12.3

Fields changed

patch: 0 => 1

resolution: => fixed
status: new => closed

Fields changed

rhbz: => 0

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

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

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