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

NSS: check if overridden shells are handled correctly in get_shell_override() #4039

Closed
sssd-bot opened this issue May 2, 2020 · 0 comments
Closed

Comments

@sssd-bot
Copy link

sssd-bot commented May 2, 2020

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

  • Created at 2016-04-26 10:29:16 by sbose
  • Closed at 2020-03-24 14:16:45 as wontfix
  • Assigned to nobody

There are various options in sssd.conf to handle missing or undefined shells, like e.g. override_shell, allowed_shells, vetoed_shells, shell_fallback and default_shell.

These options are mainly evaluated in get_shell_override() where currently only SYSDB_SHELL is taken into account but not OVERRIDE_PREFIX SYSDB_SHELL if it exists. It should be checked if a combination of the sssd.conf option together with the overridden shell will still lead to the expected reuslts.

Comments


Comment from jhrozek at 2016-05-02 09:19:57

As discussed on Thursday, let's just keep this ticket in mind and in the bugtracker and defer for now.

milestone: NEEDS_TRIAGE => SSSD Deferred


Comment from jhrozek at 2016-05-26 10:09:39

Fields changed

rhbz: => 0


Comment from sbose at 2017-02-24 14:26:22

Metadata Update from @sbose:

  • Issue set to the milestone: SSSD Patches welcome

Comment from pbrezina at 2020-03-24 14:16:44

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:16:46

Metadata Update from @pbrezina:

  • Issue close_status updated to: wontfix
  • Issue status updated to: Closed (was: Open)
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

1 participant