> On 5 Jun 2018, at 07:53, Amit <amitk...@redhat.com> wrote: > > Hello, > > Issue was opened 5 years back with following description: It is possible to > put junk into the shell attribute of an user entry. We should reuse the > existing code that is in use when allowed_shells/vetoed_shells are present, > check if the shell exists and at least give a warning. > > More on ticket: The ticket was about checking the LDAP attribute that > contains the user's shell against either /etc/shells or more preferably also > against the logic that is in sss_resp_get_shell_override and issue a warning. > > But There is a lot of code that is responder-specific and moving all this to > providers only in order to provide a warning seems like busywork. > > Can this ticket be closed?
In my opinion it can be closed. I no longer remember why we filed it and in general if nobody found the issue irritating in 5 years, it can be closed. _______________________________________________ sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org To unsubscribe send an email to sssd-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/sssd-devel@lists.fedorahosted.org/message/OATX6426WBOCJQ6S7PMKWEA2LRVC2LCC/
