#2963 GPO: Blocked access after switching from root mode to non-root mode
Closed: wontfix 4 years ago by pbrezina. Opened 8 years ago by lslebodn.

bash-4.2$ su allow_u-15330@sssdad2012.com
Password:

Message from syslogd@gs-per720-01 at Feb 25 04:40:11 ...
 sssd[be[sssdad2012.com]]:Could not open file [/var/log/sssd/gpo_child.log]. Error: [13][Permission denied]
su: System error

The subprocess gpo_child does not require extra privileges and therefore is executed in non-root mode. However the owner of this file is not changed
after switching from non-root -> root.

There should be also changed ownership of directories/files in gpo_cache/.

[root@gs-per720-01 ~]# pgrep -af sssd
23824 /bin/bash /mnt/tests/sssd/rhel72/client/ad_provider/ad_gpo_hbac/runtest
25029 /usr/sbin/sssd -D -f
25030 /usr/libexec/sssd/sssd_be --domain sssdad2012.com --uid 994 --gid 993 --debug-to-files
25031 /usr/libexec/sssd/sssd_nss --uid 994 --gid 993 --debug-to-files
25032 /usr/libexec/sssd/sssd_pam --uid 994 --gid 993 --debug-to-files

[root@gs-per720-01 ~]# ls -l /var/lib/sss/gpo_cache/
total 0
drw-------. 3 root root 21 Feb 25 04:38 sssdad2012.com

Fields changed

rhbz: => todo

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.14 backlog

Since the 1.14 branch is transitioning into maintenance mode and new functionality is being developed in master which will become 1.15 eventually, I'm mass-moving tickets from the 1.14 backlog milestone to the "Future releases" milestone.

milestone: SSSD 1.14 backlog => SSSD Future releases (no date set yet)

Metadata Update from @lslebodn:
- Issue set to the milestone: SSSD Future releases (no date set yet)

7 years ago

Metadata Update from @thalman:
- Custom field design_review reset (from 0)
- Custom field mark reset (from 0)
- Custom field patch reset (from 0)
- Custom field review reset (from 0)
- Custom field sensitive reset (from 0)
- Custom field testsupdated reset (from 0)
- Issue close_status updated to: None
- Issue tagged with: Canditate to close

4 years ago

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.

Metadata Update from @pbrezina:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

4 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/4004

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