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.

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

Closed
Rondom opened this issue May 6, 2017 · 15 comments
Closed

Entering character ö prints two characters #711

Rondom opened this issue May 6, 2017 · 15 comments

Comments

@Rondom
Copy link

Rondom commented May 6, 2017

"OpenSSH for Windows" version
0.0.12.0

OS details
Windows Server 2016 Datacenter

What is failing

  1. ssh localhost
  2. Type the character ö (or paste it from clipboard, if it is hard to enter for you)

Expected output
Character ö is printed

Actual output
Two characters ” are printed.

@bagajjal bagajjal self-assigned this Jun 8, 2017
@bagajjal bagajjal added this to the June-Mid milestone Jun 9, 2017
manojampalam pushed a commit to PowerShell/openssh-portable that referenced this issue Jun 14, 2017
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.
@bagajjal
Copy link
Collaborator

The fix is available in june-mid release..

@Rondom
Copy link
Author

Rondom commented Jun 14, 2017

Is the "june-mid-release" 0.0.15.0? If so, the issue is not fixed for me (and neither is #701)..
The behaviour is still the same with the above setup after upgrading. I have even done a reboot, it has not helped.

@bagajjal
Copy link
Collaborator

No its 0.0.16.0

@bagajjal
Copy link
Collaborator

Yet to be released

@Rondom
Copy link
Author

Rondom commented Jun 16, 2017

0.0.16.0 works now when accessing a Windows-box from Linux.
Unfortunately with the above setup and steps, now pressing ö yields for the ssh localhost case.

@bagajjal
Copy link
Collaborator

Can you check the chcp setting on the cmd.exe..

It works perfectly fine on the localhost
image

@Rondom
Copy link
Author

Rondom commented Jun 16, 2017

C:\Users\admin>echo ö
ö

C:\Users\admin>chcp
Active code page: 437

C:\Users\admin>ssh localhost
admin@WIN-U2UORB1LT7K@localhost's password:
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

admin@WIN-U2UORB1LT7K@WIN-U2UORB1LT7K C:\Users\admin>echo �     
�

admin@WIN-U2UORB1LT7K@WIN-U2UORB1LT7K C:\Users\admin>chcp         
Active code page: 437

@bagajjal
Copy link
Collaborator

I copied "ö" and pasted in the ssh window and it worked.. can you try this and see if it works...

@Rondom
Copy link
Author

Rondom commented Jun 16, 2017

Same behaviour when pasting :-(

@bagajjal
Copy link
Collaborator

  1. can you try setting the chcp to 65001
    image

  2. If it didn't work then try another terminal like putty/Cygwin.
    Linux client to windows server works fine but openssh windows client to openssh windows server doesn't work so mostly its something to windows client..

As far as I know, openssh windows client doesn't do any modification..

@Rondom
Copy link
Author

Rondom commented Jun 16, 2017

Once I do that, ö works still works locally, but when ssh-ing to localhost, it prints nothing!

@bagajjal
Copy link
Collaborator

Did you try other ssh clients (putty /Cygwin) on the same machine..

@Rondom
Copy link
Author

Rondom commented Jun 16, 2017

Just downloaded Putty, works fine.

@bagajjal
Copy link
Collaborator

bagajjal commented Jun 17, 2017

Please share your client OS details, I will try to reproduce at my end

@Rondom
Copy link
Author

Rondom commented Jun 17, 2017

It's the same as in the initial issue description: Win 2016 (10.0.14393)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants