|
Bugzilla – Full Text Bug Listing |
| Summary: | su: incorrect password -- bug or feature (documented) ? | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.3 | Reporter: | Harald Koenig <koenig> |
| Component: | Basesystem | Assignee: | Philipp Thomas <pth> |
| Status: | VERIFIED INVALID | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P4 - Low | CC: | verdelyi |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Harald Koenig
2010-07-24 18:32:17 UTC
Here's Thorsten Kukuk's response in #533249: I'm pretty sure, that all accounts, where a "su account" fails, have a locked password. Either these accounts were not created as system account but are like postgresql, or these systems were updated from old systems, were the accounts were created wrongly during installation. Or fresh created accounts without password. Solution is simple: unlock the accounts, or replace the '!' with a '*' or a valid password. Besides, that pam_unix.so seems to work but not pam_unix2.so is a well known, heavy discussed bug (see linux-pam mailing list archive). If you don't use shadow accounts (pwunconv), pam_unix.so will refuse login, too. Only the shadow case was forgotten. --------------------------------------------- #623432 has a possible solution, i.e. change the pam configuration. *** Bug 627275 has been marked as a duplicate of this bug. *** |