Bug 235653 - chpasswd(8) should support password that has more than 8 letters
chpasswd(8) should support password that has more than 8 letters
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: shadow-utils (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Peter Vrabec
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2007-04-09 05:24 EDT by Mitsuru Ogino
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-19 14:37:35 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 Mitsuru Ogino 2007-04-09 05:24:43 EDT
Description of problem:
Without the -e switch, chpasswd(8) encrypts cleartext passwords with DES
algorithm. So, only first 8 letters of the password are effective.

Version-Release number of selected component (if applicable):

How reproducible:
echo "testaccount:testpassword" | /usr/sbin/chpasswd
grep ^testaccount: /etc/shadow

Steps to Reproduce:
1. Use chpasswd(8) without -e option:
  echo "testaccount:testpassword" | /usr/sbin/chpasswd
2. Check /etc/shadow entry:
  grep ^testaccount: /etc/shadow
3. Check password field that begins with '$1$' or not.
Actual results:
The password field in /etc/shadow dose not begin with '$1$'.
The user 'testaccout' can login with password 'testpass'.

Expected results:

Additional info:
Comment 2 RHEL Product and Program Management 2007-10-19 14:37:35 EDT
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.

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