#2424 review the use of umask() in sssd code
Closed: Fixed None Opened 7 years ago by jhrozek.

Sumit noticed we use several different umask values in the sssd code. It would be nice to review them.

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.13 beta

Fields changed

mark: => 0

Fields changed

rhbz: => 0

Fields changed

milestone: SSSD 1.13 beta => SSSD 1.13 backlog

Mass-moving tickets not planned for the next two releases.

Please reply with a comment if you disagree about the move..

milestone: SSSD 1.13 backlog => SSSD 1.15 beta

Sorry, I didn't mean to move this one so far, correct umask is important security-wise.

milestone: SSSD 1.15 beta => SSSD 1.13 backlog

Re-setting priority of 1.13 backlog tickets used for planning.

priority: minor => major

Fields changed

owner: somebody => pcech
sensitive: => 0

Fields changed

status: new => assigned

Fields changed

patch: 0 => 1

First wave of patches arrived to master:
- c158450
- c4a1191
- 4230e6f
- a0ad4f2
- ae627e2
- 2f6a94e
- f8e3375
- d9c2a21
- c299f99

Fields changed

milestone: SSSD 1.13 backlog => SSSD 1.14 alpha
resolution: => fixed
status: assigned => closed

Metadata Update from @jhrozek:
- Issue assigned to pcech
- Issue set to the milestone: SSSD 1.14 alpha

5 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/3466

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.