Bug 12183 - Could password field display *'s for each character?
Summary: Could password field display *'s for each character?
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda   
(Show other bugs)
Version: 7.1
Hardware: i386 Linux
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact: Brock Organ
Keywords: FutureFeature
Depends On:
TreeView+ depends on / blocked
Reported: 2000-06-13 04:25 UTC by Brent Nordquist
Modified: 2007-04-18 16:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-09-15 19:15:12 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Brent Nordquist 2000-06-13 04:25:18 UTC
During an install, I had entered an 8-char root password twice and moved on
to later screens, when I remembered something I needed to change from an
earlier screen.  "Back" worked fine to get me there; I made the change and
started OK'ing screens to move forward again.

When I got to the root password screen again, the fields appeared blank, so
the dilemma is:  is there something there or not?  I assumed not, so I
entered the 8-char root password again.

When the install was done and upon reboot, the 8-char password didn't work,
but if I repeated it (16 chars) it worked correctly.  Clearly the previous
entry was in the buffer when I returned to the screen, but there was no way
to know that.

It seems to me that password fields should display *'s for each character,
so you can see if the field is empty or not.  If not, then I think the
fields should be cleared upon revisiting the screen.  If neither of these,
confusion will result, and the user may end up locked out of the root

Comment 1 Michael Fulbright 2000-06-15 15:43:39 UTC
This will be added for consideration for future releases.

Comment 2 Michael Fulbright 2000-09-15 19:15:10 UTC
Fixed in Pinstripe.

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