New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No disconnect handler when using exec_request #85
Comments
You're experiencing the difference between having a TTY and not. When a TTY is allocated, the SSH client will send the keystrokes immediately and supply additional information such as terminal size. With OpenSSH,
|
P.S. ctrl-c will send a signal instead when no PTY is allocated |
Thanks for the quick response! :) I am logging signals using
but nothing is coming in, the ssh client just drops back to shell.. Unfortunately because of current (already running) client implementations I can't add a I'm working on re-writing my personal proxy server from typescript to rust, so I can't change how to the clients interacts with the server. I would at the very least expect a |
It's possible that your client just kills the connection without sending a signal or a |
Hah. how did I not think of that. Thanks a bunch! :D |
Behavior is different when using
exec_request
over a "normal" connectionvs
When adding the test parameter (which will be put into an
exec_request
) data isn't received per-keystroke anymore, but only once per new-line, and a ctrl+c on the client side doesn't trigger disconnects or channel close or anything.How or when do I know on the server when a client closed / disconnected the session when they supply an argument using
exec_request
?The text was updated successfully, but these errors were encountered: