Bug 9232
Summary: | Null password badly processed | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Patrick Monnerat <patrick> |
Component: | pwdb | Assignee: | Nalin Dahyabhai <nalin> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-12-14 02:34:10 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
assigned to nalin ... seems to be fixed in RedHat 6.2 with the new version of pwdb (the same way I did!) |
After upgrade to RH6.1, I was not able to log on: my login was not password-protected (Not a NW machine!). The system always asked for a password and failed, whatever was the answer. Since "nullok" was specified in the PAM file, it should have been working. Hints for fix: My own investigations showed me that in the libpwdb/interface/unix/user.c, a test is made for "strlen(storedpassword) > 1" where the comments say " != 1"... The comment is right, since the code redirects the null password processing to a non-existent shadow password file. After fixing as above and recompiling libpwd, the null password feature is OK! I may also suggest this bug affects the "passwd" command... check