You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
none of the client executables accept "Ctrl+c" and "backspace" while feeding a password #5
changed the title [-]none of the client executable accept "Ctrl+c" and "backspace" while feeding a password[/-][+]none of the client executables accept "Ctrl+c" and "backspace" while feeding a password[/+]on Oct 8, 2015
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.
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.
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.
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.
Activity
[-]none of the client executable accept "Ctrl+c" and "backspace" while feeding a password[/-][+]none of the client executables accept "Ctrl+c" and "backspace" while feeding a password[/+]quamrulmina commentedon Oct 10, 2015
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 commentedon Oct 13, 2015
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 commentedon Oct 20, 2015
There shouldn't be any "*" when entering a password.
There shouldn't be any "*" when entering a password or passphrase
quamrulmina commentedon Oct 21, 2015
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 commentedon Oct 29, 2015
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 commentedon Nov 11, 2015
The latest release should have this fixed.
Update winget.yml (#5) (#2054)
Update winget workflow (#2280)
Add agentic issue-triage workflow for Win32-OpenSSH (#2443)