Bug 4077 - passwd does not add password to empty field
passwd does not add password to empty field
Product: Red Hat Linux
Classification: Retired
Component: passwd (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Cristian Gafton
Depends On:
  Show dependency treegraph
Reported: 1999-07-16 14:06 EDT by mw
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-09-20 11:14:46 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 mw 1999-07-16 14:06:31 EDT
When the password field is empty in /etc/passwd, passwd does
not add the encrypted passwd to the field, and it does not
indicate it with an error.

Here is the complete experiment:

# useradd okidoki
# grep okidoki /etc/passwd
# emacs /etc/passwd         (empty password field)
# grep okidoki /etc/passwd
# passwd okidoki
Changing password for user okidoki
New UNIX password:                     (typed MaciLaci)
Retype new UNIX password:              (MaciLaci)
passwd: all authentication tokens updated successfully
root@moni: ~
# grep okidoki /etc/passwd

How can this be a problem (besides, that I think it is not a
correct behavior) since RH 6.0 does not let you log in w/o
an empty passwd field?

Well, imagine that on a yp server, after emptying the passwd
field, I run passwd (thinking passwd is set), then run

(cd /var/yp; make)

Now, on another older (5.2) RH box on the same NIS domain, I
could log in as okidoki w/o a passwd!  (I ran this
experiment with a 5.2 box as a yp server but passwd-0.58-1
and pwdb-0.58-3 installed).

Let me remark that yppasswd seems to behave correctly, but
linuxconf also gets confused (I guess it is running passwd).

Mate Wierdl
Comment 1 Jay Turner 1999-07-19 10:44:59 EDT
This has been confirmed in the test lab.
Comment 2 Cristian Gafton 1999-09-20 11:14:59 EDT
Should be fixed in the next release.

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