Bug 1372226

Summary: Dialog asks for password but it is username.
Product: [Fedora] Fedora Reporter: Raphael Groner (DAASI International) <raphael.groner>
Component: ksshaskpassAssignee: Aurelien Bompard <aurelien>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 24CC: aurelien
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 16:58:12 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:
Attachments:
Description Flags
sample none

Description Raphael Groner (DAASI International) 2016-09-01 08:12:55 UTC 
Description of problem:
There's a dialog to ask for the username but the label for the text input field says Password. An user may tend to enter its password (whatever for a given user name). This password is shown in the next dialog as the user name, this second dialog asks for the "real" password.

Version-Release number of selected component (if applicable):
ksshaskpass-5.7.3-1.fc24.x86_64
git-2.7.4-2.fc24.x86_64

How reproducible:
always

Steps to Reproduce:
1. login to a plasma5 session
2. open terminal
3. git pull origin master

Actual results:
ksshaskpass pops up a dialog that asks for password or user, it's not clear what it wants to get entered.

Expected results:
The dialog asks for either user name or password, not both. There's nowhere the password shown in clear text.

Additional info:
Maybe this is a translation bug? Or is it because there's one dialog template only with a fixed label value.
This is a security issue because it's possible to see the password in clear text.
Comment 1 Raphael Groner (DAASI International) 2016-09-01 08:16:07 UTC 
Duplication in bug #1018814 with EOL.
Comment 2 Raphael Groner (DAASI International) 2016-09-01 08:17:20 UTC 
 David Jones 2016-03-10 15:31:16 EST

This thread explains the reason for this issue, and offers a potential work-around.

http://git.661346.n2.nabble.com/Git-ksshaskpass-to-play-nice-with-https-and-kwallet-td6858195.html
Comment 3 Raphael Groner (DAASI International) 2016-09-01 08:17:47 UTC 
Created attachment 1196618 [details]
sample
Comment 4 Fedora End Of Life 2017-07-25 22:47:30 UTC 
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Comment 5 Fedora End Of Life 2017-08-08 16:58:12 UTC 
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.