[Bug 3723] sshd failed to close session when client specifies no remote command

[bugzilla-daemon at mindrot.org]

https://bugzilla.mindrot.org/show_bug.cgi?id=3723

--- Comment #2 from S Zhang <szhang at gen-info.osaka-u.ac.jp> ---
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.