Bug 453875 - RHEL5.2 OpenSSH section corrections
RHEL5.2 OpenSSH section corrections
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: Deployment_Guide (Show other bugs)
All Linux
low Severity low
: rc
: ---
Assigned To: Jaromir Hradilek
: Documentation
Depends On:
  Show dependency treegraph
Reported: 2008-07-02 19:27 EDT by Michael Hideo
Modified: 2016-06-17 17:10 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-08-10 12:34:59 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michael Hideo 2008-07-02 19:27:37 EDT

there are at least two errors:

1) The statement "This process will not work if the user logs in using
the SSH protocol." is incorrect. I have successfully tested this with

2) The order of the steps 1-3 is wrong. I believe a simple chage -d 0
username will do the trick, but even running usermod -p "" updates the
chage results so that the password is not expired, so running step 3
negates step 2. I am also not sure why step 1 is necessary.

Thanks for your attention!

-- Hydraulic Engineer, Water Resources Group UC Regional Office, Bureau of
Reclamation work: 801-524-3879 fax: 801-524-3847
Comment 4 Jaromir Hradilek 2010-05-28 05:55:35 EDT
Changed status to ON_QA.

What I've done is as follows:

  * Removed the SSH-related statement as suggested in the
    original bug report; there is no reason for SSH not to
    work in this case, and I have successfully checked that
  * Removed redundant `usermod -L <username>' step.
  * Added reference to Shadow Passwords section.
  * Added `-l' to the list of useradd command line options.
  * Changed the order of steps as suggested in the bug report:
    the original order was not correct and could not work at
  * Rephrased some sentences where necessary.

Note You need to log in before you can comment on or make changes to this bug.