PowerShell / PowerShell/Win32-OpenSSH

internal network connection hold

Open
#1,448 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue-Discussion-Deprecated/use GitHub discussions
Dominant language
No language data
Stars
8.3k
Forks
819
PR merge metrics
No merged PRs in 30d

Description

"OpenSSH for Windows" version
8.0.0.0
Server OperatingSystem
Windows Server 2012 R2 Datacenter
Client OperatingSystem
WIN 10
What is failing

use sshj execute command:
DefaultConfig defaultConfig = new DefaultConfig(); SSHClient sshClient = new SSHClient(defaultConfig); sshClient.addHostKeyVerifier(new PromiscuousVerifier()); sshClient.connect(authModel.getHost(), authModel.getPort()); sshClient.authPassword(authModel.getUsername(), authModel.getPassword()); sshClient.setTimeout(15000); try (Session session = sshClient.startSession()) { Session.Command instance = session.exec(command); String result = IOUtils.readFully(instance.getInputStream()).toString(StandardCharsets.ISO_8859_1.name()); result = result + IOUtils.readFully(instance.getErrorStream()).toString(StandardCharsets.ISO_8859_1.name()); textPane.insertMessage(result); }
Expected output
list directory
Actual output
hold

errors****
Server network environment is intranet,when i check server eventviewer openssh log,found only one recode :
sshd: Accepted password for Administrator from 127.0.0.1 port 27656 ssh2
not found Received disconnect info

why sshd accetped password from 127.0.0.1?

i think this is the key to hold

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

Start with the provided Java sshj connection snippet and the Windows Server 2012 R2 OpenSSH event log entry showing an accepted password from 127.0.0.1. Reproduce the command-hang behavior in the stated client and server environment, then compare the client output and server disconnect events. Done means the cause of the hold is identified and command execution completes or fails with a clear diagnostic.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.