Damien Miller
2023-Apr-08 04:46 UTC
Killing the OpenSSH server doesn't cause the Windows OpenSSH client to die
On Fri, 7 Apr 2023, Yuri wrote:> The fact that '-o ServerAliveInterval=50' makes no difference suggests that > there is a bug in the OpenSSH client. > It either fails to sent heartbeats, or it gets stuck in some Windows system > call and this makes it to fail to send heartbeats.without debug logs from both the client and server in this situation, it's not really possible to say what is going on. Bear in mind that the Portable OpenSSH project and the Windows OpenSSH project are separate. They use our code, but do a number of things quite differently so if you suspect a problem in their code then they are the ones to contact (e.g. via a github issue). -d
Yuri
2023-Apr-08 05:20 UTC
Killing the OpenSSH server doesn't cause the Windows OpenSSH client to die
On 4/7/23 21:46, Damien Miller wrote:> without debug logs from both the client and server in this situation, it's > not really possible to say what is going on.What are the options that I should use to generate logs? Yuri
Reasonably Related Threads
- Killing the OpenSSH server doesn't cause the Windows OpenSSH client to die
- Killing the OpenSSH server doesn't cause the Windows OpenSSH client to die
- Killing the OpenSSH server doesn't cause the Windows OpenSSH client to die
- Killing the OpenSSH server doesn't cause the Windows OpenSSH client to die
- Killing the OpenSSH server doesn't cause the Windows OpenSSH client to die