-
Notifications
You must be signed in to change notification settings - Fork 767
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.
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
Entering character ö prints two characters #711
Comments
Support the unicode characters as input to the ssh client. PowerShell/Win32-OpenSSH#711 Remove the bAnsi related code changes to the ssh-shellhost.c as that code never executes.. Fixed "long pressing key issue for the slow ssh connections" PowerShell/Win32-OpenSSH#701 fixed warning message in the latestw_all recent commits. Fixed the issue with ssh failures in the latestw_all recent commits.
The fix is available in june-mid release.. |
Is the "june-mid-release" 0.0.15.0? If so, the issue is not fixed for me (and neither is #701).. |
No its 0.0.16.0 |
Yet to be released |
0.0.16.0 works now when accessing a Windows-box from Linux. |
|
I copied "ö" and pasted in the ssh window and it worked.. can you try this and see if it works... |
Same behaviour when pasting :-( |
As far as I know, openssh windows client doesn't do any modification.. |
Once I do that, ö works still works locally, but when ssh-ing to localhost, it prints nothing! |
Did you try other ssh clients (putty /Cygwin) on the same machine.. |
Just downloaded Putty, works fine. |
Please share your client OS details, I will try to reproduce at my end |
It's the same as in the initial issue description: Win 2016 (10.0.14393) |
"OpenSSH for Windows" version
0.0.12.0
OS details
Windows Server 2016 Datacenter
What is failing
ssh localhost
ö
(or paste it from clipboard, if it is hard to enter for you)Expected output
Character
ö
is printedActual output
Two characters
”
are printed.The text was updated successfully, but these errors were encountered: