PowerShell / PowerShell/Win32-OpenSSH
Localized socket error messages are shown as octal numbers
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 8.3k
- Forks
- 819
- PR merge metrics
- No merged PRs in 30d
Description
Troubleshooting steps
https://github.com/PowerShell/Win32-OpenSSH/wiki/Troubleshooting-Steps
Terminal issue? please go through wiki
https://github.com/PowerShell/Win32-OpenSSH/wiki/TTY-PTY-support-in-Windows-OpenSSH
Please answer the following
"OpenSSH for Windows" version
((Get-Item (Get-Command sshd).Source).VersionInfo.FileVersion)
8.1.0.1
Server OperatingSystem
((Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows nt\CurrentVersion\" -Name ProductName).ProductName)
N/A
Client OperatingSystem
Windows 10 Build 20190
What is failing
When I try connecting to a non-exist server, I saw some bizarre error messages.
Expected output
The localized message are shown properly, or just show English ones.
Actual output
The localized message are shown as octal representations.
ssh: Could not resolve hostname nanopim4: \262\273\326\252\265\300\325\342\321\371\265\304\326\367\273\372\241\243
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the hostname-resolution failure described in the report on Windows 10 and review the linked troubleshooting guidance. Trace how the localized socket error is formatted in Win32-OpenSSH; done means the error appears as readable localized text or English rather than octal representations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100