PowerShell / PowerShell/Win32-OpenSSH
OpenSSH Windows 10 Dynamic port forwarding: Desktop -> gateway -> target_server
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 8.3k
- Forks
- 819
- PR merge metrics
- No merged PRs in 30d
Description
I connect today from my Windows 10 desktop to a gateway (Linux jumphost) and from there to 10+ Linux target_servers in 2 different ways:
-
In CMD
...............A) ssh ab028583@gateway/jumpserver
...............B) from jumpserver ssh ab028583@target_server
...............C) I am prompted twice for password.
...............D) This works fine but it is cumbersome and not practical. -
With a Putty session including
...............A) Host Name="jumpserver" IP
...............B) "Remote Command"=ssh -L8081:localhost:8080 ab028583@target_server
...............C) Tunnels="L8081 localhost:8081"
...............D) This also works fine but it is cumbersome and not practical.
Method 2) opens a tunnel and "localhost:8081" in a browser connects to target_server
Both methods above work very well but are non practical and time out quickly.
I don't create any SSH-keys at least that I know.
I need to implement an openSSH script to connect to each of the Linux target servers, including the userid and pwd in the script so I dont have to type it for each login.
Also I would like to include flags so the connection does not time out:
-o ServerAliveInterval=10 -o ServerAliveCountMax=15
Can anyone help me on how such a script looks like?
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 repository file, test, or entry point is identified; start by reviewing the issue's Windows OpenSSH, gateway, dynamic forwarding, and keepalive requirements. Done would be documented guidance or a supported script approach that addresses login credentials, target-server access, port forwarding, and timeout settings.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, networking
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100