Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GPO: Blocked access after switching from root mode to non-root mode #4004

Closed
sssd-bot opened this issue May 2, 2020 · 1 comment
Closed

Comments

@sssd-bot
Copy link

sssd-bot commented May 2, 2020

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/2963

  • Created at 2016-02-25 10:44:44 by lslebodn
  • Closed at 2020-03-24 14:05:37 as wontfix
  • Assigned to nobody

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

Comments


Comment from jhrozek at 2016-02-26 10:52:53

Fields changed

rhbz: => todo


Comment from jhrozek at 2016-02-26 11:01:26

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.14 backlog


Comment from jhrozek at 2016-12-15 11:01:16

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)


Comment from lslebodn at 2017-02-24 14:26:55

Metadata Update from @lslebodn:

  • Issue set to the milestone: SSSD Future releases (no date set yet)

Comment from thalman at 2020-03-13 11:53:26

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

Comment from pbrezina at 2020-03-24 14:05:36

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.


Comment from pbrezina at 2020-03-24 14:05:38

Metadata Update from @pbrezina:

  • Issue close_status updated to: wontfix
  • Issue status updated to: Closed (was: Open)
@alexey-tikhonov
Copy link
Member

Currently this is handled by packaging (RHEL).
Fedora spec-files doesn't take care of this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants