|Summary:||Procedure for changing passwords for new user account is inaccurate|
|Product:||[Retired] Red Hat Linux||Reporter:||Karsten Wade <kwade>|
|Component:||rhl-sap||Assignee:||Ed Bailey <ed>|
|Status:||CLOSED RAWHIDE||QA Contact:||Tammy Fox <tammy.c.fox>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2003-02-21 17:06:43 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Karsten Wade 2003-01-23 06:36:12 UTC
Description of problem: In the last section of the above page, New User Passwords, a method is described which is technically inaccurate. First are the actual issues, then a suggested fix. Issues: 1. 'chage -d 0' should read 'chage -d 0 <username>' 2. '/usr/sbin/usermod -p "<password>"' should read '/usr/sbin/usermod -p "<password>" <username>' -- the username should be appended, as in 1. above 3. '/usr/sbin/usermod -p "<password>" <username>' puts an unecrypted password in /etc/shadow, and there will be no way to login (this effectively disables the account). When looking for a solution, it becomes obvious that /usr/bin/passwd would be a better choice. Also, leading people down the path of null passwords is risky business, at best. See follow-up for a plain text "patch". Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Open up the URL above 2. Read the paragraphs 3. Actual results: Inaccurate technical information Expected results: Accurate technical information :) Additional info:
Comment 1 Karsten Wade 2003-01-23 06:46:08 UTC
Created attachment 89545 [details] plain text "patch" for issue described This is a plain text suggestion for fixing this error. This is the fix that I propose to use in related documentation. I can supply the actual markup used for this, but don't recommend using the entire file as it is customized for another version of RHL and could therefore contain other inaccuracies against RHL 8.0.
Comment 2 Ed Bailey 2003-02-21 17:06:43 UTC
These issues will be addressed in the next released version of the manual. Thanks for the feedback!