Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Closed
manojampalam opened this issue Oct 8, 2015 · 6 comments
Closed

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

manojampalam opened this issue Oct 8, 2015 · 6 comments

Comments

@manojampalam
Copy link
Contributor

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
@manojampalam manojampalam 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 Oct 8, 2015
@quamrulmina
Copy link
Contributor

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
Copy link
Contributor Author

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
Copy link

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

quamrulmina added a commit that referenced this issue Oct 21, 2015
@quamrulmina
There shouldn't be any "*" when entering a password or passphrase
89452c8 
There shouldn't be any "*" when entering a password or passphrase for
better security. Linux/Unix openssh works the same way - without any
"*". Great suggestion by Mark Hahnel in comments of Issue #5
@quamrulmina
Copy link
Contributor

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.

@godefroi godefroi mentioned this issue Oct 21, 2015
Closed
@quamrulmina
Copy link
Contributor

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
Copy link
Contributor Author

The latest release should have this fixed.

tgauth added a commit that referenced this issue Apr 13, 2023
@tgauth
Update winget.yml (#5) (#2054)
e574bb3
tgauth added a commit that referenced this issue Oct 10, 2024
@tgauth
Update winget workflow (#2280)
e5a9144 
* Update winget.yml (#5)

* Update winget.yml
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@markhaehnel @manojampalam @quamrulmina