You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to reopen #1667 since it appeared in a setup.
The git-for-windows ssh-client crashes with Exception thrown at 0x00000002101B5FE4 (msys-2.0.dll) in ssh.exe: 0xC0000005: Access violation writing location 0x0000000800300000.
when connecting to another Windows Server with OpenSSH-Server.
It happens as soon as the shell request is accepted.
Client verbose log just says: debug2: shell request accepted on channel 0
=> dead
All I do to trigger or fix it is to switch between git-for-windows Version Git-2.28.0-64-bit and Git-2.44.0-64-bit.
Git-2.28.0-64-bit works fine, Git-2.44.0-64-bit crashes when connecting to Windows Servers with SSH.
The systems ssh-client installed by Microsofts OpenSSH-Port works fine.
Expected behavior
ssh.exe doesn't crash when open (power)shell on windows ssh server
Description / Steps to reproduce the issue
I would like to reopen #1667 since it appeared in a setup.
The git-for-windows ssh-client crashes with
Exception thrown at 0x00000002101B5FE4 (msys-2.0.dll) in ssh.exe: 0xC0000005: Access violation writing location 0x0000000800300000.
when connecting to another Windows Server with OpenSSH-Server.
It happens as soon as the shell request is accepted.
Client verbose log just says:
debug2: shell request accepted on channel 0
=> dead
All I do to trigger or fix it is to switch between git-for-windows Version Git-2.28.0-64-bit and Git-2.44.0-64-bit.
Git-2.28.0-64-bit works fine, Git-2.44.0-64-bit crashes when connecting to Windows Servers with SSH.
The systems ssh-client installed by Microsofts OpenSSH-Port works fine.
Expected behavior
ssh.exe doesn't crash when open (power)shell on windows ssh server
Actual behavior
ssh.exe crashes
Verification
Windows Version
MINGW64_NT-10.0-20348
Are you willing to submit a PR?
No response
The text was updated successfully, but these errors were encountered: