PowerShell / PowerShell/Win32-OpenSSH
X11 forwarding and Control Sockets
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 8.3k
- Forks
- 819
- PR merge metrics
- No merged PRs in 30d
Description
Summary of the new feature / enhancement
I constantly use windows implementation of openSSH through VSCode and the server I connect to now uses two factor authentication. The lack of x11 forwarding and control sockets means that:
a) I need to have a separate ssh through wslg to run my code with x11 support.
b) Every time openSSH drops the connection I need to reauthenticate it with my 2FA authenticator.
Given that wslg has incorporated support for x-windows, I don't see the technical limitation of using it for openSSH tunnels.
Also, I don't understand why the keepalive sockets don't work on Windows.
Proposed technical implementation details (optional)
No response
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
No files, tests, or entry points are named. Start by reviewing the Win32-OpenSSH implementation and existing support for X11 forwarding and control sockets, then determine how Windows and WSLg affect both features. Done means the requested forwarding and socket behavior works on Windows without the separate WSLg SSH session or repeated authentication.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100