Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 901008 (JBPAPP6-1117)

Summary: Installer :Password input should show special characters(standard *) instead of blank in cli mode
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Madhumita Sadhukhan <msadhukh>
Component: InstallerAssignee: Thomas Hauser <thauser>
Status: CLOSED WONTFIX QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 6.0.0CC: aszczucz, msadhukh, pslavice, thauser
Target Milestone: ---   
Target Release: EAP 6.0.1   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBPAPP6-1117
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-11-08 10:01:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
CLI_passwordinput-6.0.1.ER2.png none

Description Madhumita Sadhukhan 2012-10-05 07:59:18 UTC 
project_key: JBPAPP6

It is confusing when user tries to enter password in cli mode as it cant be seen how many characters is entered(attaching screenshot)

Please replace this with special characters(*) as per standard.
Comment 1 Madhumita Sadhukhan 2012-10-05 07:59:52 UTC 
Attachment: Added: CLI_passwordinput-6.0.1.ER2.png
Comment 2 Alex Szczuczko 2012-10-05 14:07:28 UTC 
Hmm, interesting. The choice between blanking and and non-printing password prompts is a choice between letting the user know their input is being received, and not leaking the number of characters that the password has.

The CLI standard in most *nix programs is to not show any blanking characters (ssh, su, sudo, etc.). However, the GUI standard in most *nix programs is to show blanking characters (GUI login managers), which is consistent with the general standard of Windows, which always shows blanking characters.

I would think that because we're discussing a CLI tool, which is consistent with the *nix CLI standard, that we shouldn't add blanking characters. In the case where the user is used to the Windows standard, Windows CLI almost never has password entry prompts, so there isn't a clear expectation of what to expect on CLI.
Comment 3 Thomas Hauser 2012-10-05 18:25:29 UTC 
Based on what Alex states above, I believe that we should leave the installer password prompt as is. If this changes, we can reopen this issue.
Comment 4 Misty Stanley-Jones 2012-11-05 05:55:24 UTC 
Release Notes Docs Status: Added: Not Required
Comment 5 Anne-Louise Tangring 2012-11-13 20:28:10 UTC 
Release Notes Docs Status: Removed: Not Required 
Docs QE Status: Removed: NEW