PowerShell / PowerShell/Win32-OpenSSH

SFTP Logoff issue with OPENSSH

Open
#1,886 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
8.3k
Forks
819
PR merge metrics
No merged PRs in 30d

Description

SftpClient: IPWORKSSSH sftp client
SftpServer: OpenSSH Sftp server

Getting below exception at client while connecting sftp server: "System Error: Connection reset"
Checked with IPWORKSSSH sftp client team and received below response

"""
The error and Wireshark trace indicate that the server decided to end the connection by resetting it (instead of gracefully ending
it). It is not clear why.
It could just be that this is how this specific server prefers to close the connection or perhaps it did not like/understand the last
packet sent from the client. A simple way to handle this would be to catch the exception and continue on -- the connection has
been closed.
"""
Requesting to confirm above is expected or any improvement is required at openSSH server side for graceful termination.

Please answer the following

OpenSSH version -> OpenSSH_for_Windows_7.6p1, LibreSSL 2.6.4
Server OperatingSystem -> Windows 10
Client OperatingSystem -> Windows 10
What is failing -> Getting exception while connecting to OpenSSH server
Expected output -> Graceful termination
Actual output -> Connection is getting abnormal termination

Attaching Wireshark trace and exception details.

Exception

wireshark_image

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 attached Wireshark trace and exception details, then review the reported OpenSSH_for_Windows_7.6p1 server and Windows 10 environment. Determine whether the reset occurs during SFTP logoff because of server behavior or an incompatible final packet; done means identifying a reproducible cause and whether a server-side change is required.

Written by the indexing model from the issue text.

Assessment

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.