Bug 5005
Summary: | See bug 3281 | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | theman |
Component: | passwd | Assignee: | Cristian Gafton <gafton> |
Status: | CLOSED NEXTRELEASE | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 6.0 | CC: | karl, rhbzill |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 1999-09-20 15:06:26 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: |
Description
theman
1999-09-09 01:22:32 UTC
*** Bug 3281 has been marked as a duplicate of this bug. *** Am I going crazy? I installed Red Hat 6.0 (`Everything'), all was well, I logged in as root on the console, typed passwd operator to enable a non-root account, it said passwd: all authentication tokens updated successfully but /etc/passwd didn't actually change, the password was still *. I tried several different passwords. I did not enable MD5 passwords or NIS+ on the new setup screen at the end. This is not peculiar to operator. For example, I just tried passwd bin (another account with a * password), used jac:jil! for the password, and /etc/passwd didn't change despite the success message. ------- Additional Comments From jbj 06/05/99 11:12 ------- Change the password field from '*' to '!!' and you will be able to change the password. ------- Additional Comments From theman.edu 09/08/99 21:17 ------- This is not reasonable. No other unix does anything this stupid. Root using passwd to change the entry should ALWAYS work, no matter the existing contents. WHAT THE HELL WERE YOU THINKING? It will be fixed in the next release. The passwd of the accound does not change (the account still remains locked), so I fail to see why this is a Security/High bug. |