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

PAM: check if overriden shells are handled correctly in the PAM responder #4038

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

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

In pam_check_user_search() both sysdb_search_user_by_upn() and sysdb_getpwnam_with_views() are used. Although it looks like currently the override data is not evaluated by te PAM responder we should be consistent here and make sure the result of the upn search has the overide data as well.

Comments


Comment from sbose at 2016-04-26 10:29:42

Fields changed

type: defect => task


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

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:13:22

Fields changed

rhbz: => 0


Comment from sbose at 2017-02-24 14:59:17

Metadata Update from @sbose:

  • Issue set to the milestone: SSSD Patches welcome

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

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:47

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