none of the client executables accept "Ctrl+c" and "backspace" while feeding a password

[manojampalam]

Issue observed with ssh.exe (while feeding password) and ssh-keygen.exe (while feeding paraphrase)

Ex.
C:\openssh>ssh-keygen.exe -t rsa -f id_rsa
Generating public/private rsa key pair.
Enter passphrase (empty for no passphrase): **************

When asked to enter passphrase, try Ctrl+C or backspace

[quamrulmina]

Control-Break works instead of Control-C to get out of session, we will try to fix it to accept control-c for exiting like in openssh Linux.
But we tested backspace processing to work in ssh.exe client during password typing or giving passphrase. ssk-keygen.exe backspace processing also works when giving passphrase. Can you kindly retest your scenario with the latest binaries. Control-C is a problem but backspace should not be.

[manojampalam]

Tested on latest binaries. backspace does work but does not reflect on the input password mask (I'm testing on Windows 10) - i.e the "*"s do not get deleted on a backspace stroke. This is not a pressing issue and we can take care of this later.

[markhaehnel]

There shouldn't be any "*" when entering a password.

[quamrulmina]

Fixed it and checked in the code. Great suggestions – Linux/Unix openssh works the same way – no “*” feedback in password or passphrase.
Thanks. Quamrul Mina.
From: Mark Hähnel [mailto:notifications@github.com]
Sent: Tuesday, October 20, 2015 1:55 AM
To: PowerShell/Win32-OpenSSH
Cc: Quamrul Mina
Subject: Re: [Win32-OpenSSH] none of the client executables accept "Ctrl+c" and "backspace" while feeding a password (#5)

There shouldn't be any "*" when entering a password.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/5#issuecomment-149454658.

[quamrulmina]

Fixed in L1 branch. Control-c is now sent to the sshd server and will not terminate ssh.exe client itself. To terminate or abandon client, type Control-break. Backspace also now works when typing password.

[manojampalam]

The latest release should have this fixed.