Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Win32 OpenSSH eats up encoding for any sixel images

Open
#2,439 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
c, powershell

Research direction

Reproduce the reported Windows Terminal -> pwsh.exe -> ssh.exe -> sshd.exe -> pwsh.exe pipeline with C:\snake.six, then trace where the sixel-encoded text is lost. Done means the same command preserves the image data and displays the sixel image through Win32 OpenSSH.

Written by the indexing model from the issue text.

Description

Area-Terminal Investigate Up-For-Grabs
Prerequisites
  • Write a descriptive title.
  • Make sure you are able to repro it on the latest version
  • Search the existing issues.
Steps to reproduce

My current pipeline is Windows Terminal -> pwsh.exe -> ssh.exe -> WEB -> sshd.exe -> pwsh.exe -> type C:\snake.six

When I print out snake.six which is a text file with a sixel-encoded image I get nothing.

Expected behavior
PS> type C:\snake.six
[should display image]
PS>
Actual behavior
PS> type C:\snake.six

PS>
Error details

Environment data
Name                           Value
----                           -----
PSVersion                      7.6.2
PSEdition                      Core
GitCommitId                    7.6.2
OS                             Microsoft Windows 10.0.26200
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.4
SerializationVersion           1.1.0.1
WSManStackVersion              3.0
Version

OpenSSH_for_Windows_10.0p2 Win32-OpenSSH-GitHub, LibreSSL 4.2.0

Visuals
Image Image
Dominant language
No language data
Stars
8.3k
Forks
820
Avg merge
12m
Merged PRs (30d)
1

Getting set up

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.

More from PowerShell/Win32-OpenSSH

All issues in PowerShell/Win32-OpenSSH

Similar issues

More Networking issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.