CTRL-C in ssh included with git kills the pipe

Duffey, Blake· Jun 2, 2023, 21:55 UTC · lore

The version of OpenSSH included with git 2.41 reports as: OpenSSH_9.3p1, OpenSSL 1.1.1u 30 May 2023

The version of OpenSSH available from https://github.com/PowerShell/Win32-OpenSSH/releases reports as: OpenSSH_for_Windows_9.2p1, LibreSSL 3.7.2

If I connect to server X with the first client, run top, and issue CTRL-C - I get client_loop: send disconnect: Broken pipe

If I connect to server X with the second client, run top, and issue CTRL-C... it ends top and the connection remains

brian m. carlson· Jun 2, 2023, 22:52 UTC · re: Duffey, Blake · lore

Re: CTRL-C in ssh included with git kills the pipe

On 2023-06-02 at 21:55:21, Duffey, Blake wrote:

Show 11 quoted lines

> The version of OpenSSH included with git 2.41 reports as:
> OpenSSH_9.3p1, OpenSSL 1.1.1u 30 May 2023
> 
> The version of OpenSSH available from https://github.com/PowerShell/Win32-OpenSSH/releases reports as:
> OpenSSH_for_Windows_9.2p1, LibreSSL 3.7.2
> 
> If I connect to server X with the first client, run top, and issue CTRL-C - I get
> client_loop: send disconnect: Broken pipe
> 
> If I connect to server X with the second client, run top, and issue CTRL-C...
> it ends top and the connection remains

The Git project does not ship anything but source code. It sounds like you're using Git for Windows, which does ship a variety of software, including OpenSSH. Assuming that's the case, you may want to go to their issue tracker, at https://github.com/git-for-windows/git/issues/, to report this, after verifying that there's not already an issue for this. That being said, it looks like https://github.com/git-for-windows/git/issues/3848 may be the issue you're reporting.

-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA