Bug #1188
[parabola-hacekrs-nshd] PAM configuration causes confusing "unknown user" messages.
Status:
fixed
Priority:
bug
Assignee:
% Done:
100%
Description
Because if nshd says "no" (perhaps the password was wrong) it tries the next db backend (files or compat or whatever), where the user doesn't exist.
History
Updated by lukeshu over 6 years ago
- % Done changed from 0 to 100
- Assignee set to lukeshu
- Status changed from open to fixed
This has been resolved by having PAM only talk directly to it for the password stack (change password); and otherwise only talk to it through NSS.