PowerShell / PowerShell/Win32-OpenSSH

How to _not_ use UTF-8 (connection to server with LANG="en_US.iso885915")?

Open
#1,855 13 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
8.3k
Forks
819
PR merge metrics
No merged PRs in 30d

Description

"OpenSSH for Windows" version
OpenSSH_for_Windows_8.6p1, LibreSSL 3.3.3

Server OperatingSystem
RHEL7, CentOS8 (likely doesn't matter)

Client OperatingSystem
Windows Server 2019 Datacenter

What is failing
The server and a bunch of tools installed must use iso885915 encoding, so that is set globally via LANG="en_US.iso885915.
When connecting to the server with PuTTY and configured "Remote character set" ISO-8859-15: 1999 (Latin-9, "euro") (found under Configuration->Window->Translation) then everything works fine - tools generate output in that character set, the client can display them properly and when entering data it gets in as expected.

But that isn't the case with OpenSSH :-(

Expected output
With PuTTY

> echo ä| hexdump
0000000 0ae4
0000002
> printf \\xe4\\n
ä
>

Actual output
With OpenSSH

> echo ä | hexdump
0000000 a4c3 000a
0000003
> printf \\xe4\\n

>

Is there any way with this OpenSSH version to not use UTF-8?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report identifies OpenSSH_for_Windows_8.6p1 and compares its output with PuTTY using LANG="en_US.iso885915" and the shown echo, hexdump, and printf commands. Start by reproducing those commands on the stated Windows and RHEL/CentOS setup, then inspect the issue discussion for the supported character-set configuration. Done means establishing whether ISO-8859-15 can be selected and documenting the result or limitation.

Written by the indexing model from the issue text.

Assessment

Domain
networking, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.