https://bugzilla.mindrot.org/show_bug.cgi?id=3723
--- Comment #2 from S Zhang <[email protected]> --- I was on RHEL 8.10 and Oracle 8.10. I am currently testing it on other distros. I believe that the systemd session was created via PAM, but somehow even if the sshd failed to create the remote session, as no remote executable was specified by -N, the client side did not know that the session failed, thus the connection remains. Maybe systemd sees that the connection survived and did not close their session/scope as well. Are there any conditions for the server to initiate close connection, and which side initiated the connection close sequence when the server side failed to create a session due to pam_limits.so? -- You are receiving this mail because: You are watching someone on the CC list of the bug. You are watching the assignee of the bug. _______________________________________________ openssh-bugs mailing list [email protected] https://lists.mindrot.org/mailman/listinfo/openssh-bugs
