The OpenSSH daemon is supposed to start, and fork off additional daemons for new connections, to prevent the loss of the main daemon from killing vital, long-running, active connections. Various tools have tried to mandate the end of client sessions, for various reasons and by various mens, Please don't try to "improve security" by breaking long-standing features. This feature, in particular, allows a remote administrator to revise the SSH configuration, restart it for validation, and not lose the existing remote shell session to allow reverting a risky chnage. Such changes would become *vastly* more risky, and very difficult to revert due to the now broken sshd configuration. Been there, done that. Last Tuesday..... On Fri, Apr 7, 2023 at 12:18 PM Yuri <yuri@xxxxxxxxx> wrote: > > I connect with the OpenSSH client on Windows to the OpenSSH server on > FreeBSD, all in one LAN, Wifi to Eithernet. > > > After a while, usually when the connection is inactive for some time, it > becomes dysfunctional: it becomes impossible to connect through reverse > port forwards from FreeBSD to Windows. > > At such times killing the ssh server process on FreeBSD, corresponding > to the connection, doesn't cause the client to exit on Windows. > > But hitting Enter on the client in Windows causes it to immediately exit. > > > Did anybody experience a problem like this? > > Could there be a bug in OpenSSH? > > Is it possible that Windows fails to deliver the signal to the client > that the connection was terminated? > > > Thank you, > > Yuri > > _______________________________________________ > openssh-unix-dev mailing list > openssh-unix-dev@xxxxxxxxxxx > https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev _______________________________________________ openssh-unix-dev mailing list openssh-unix-dev@xxxxxxxxxxx https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
