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
Issue with isConnected/isAuthenticated after remote terminal restart #1983
Comments
In-so-far as socket tests go
If One problem with I suppose an SSH_MSG_IGNORE could be sent, instead. That one wouldn't require a response from the server but it's easy to imagine scenarios wherein the server would have still "closed" the connection even if the client was able to successfully send packets (phpseclib's Really, I don't think there's a perfect way to implement What if I add a |
libssh's In fact, phpseclib's |
I suppose something else I could do is to give
|
How does terrafrost@d27429a look to you? I'll merge it into the 3.0 branch in a few days unless you (or anyone really lol) reply sooner then that with some reason as to why I shouldn't! (also, I don't like |
terrafrost@d27429a has been merged. |
Description of the Issue:
I am encountering an issue with the phpseclib library regarding the isConnected and isAuthenticated methods. After restarting the remote terminal, these methods continue to return true, even though logically the connection should be lost.
Additional Details:
Steps to Reproduce the Issue:
Expected Behavior:
After restarting the remote terminal, it is expected that the isConnected and isAuthenticated methods return false to indicate the loss of connection.
Thank you for your assistance in resolving this problem.
Best regards,
The text was updated successfully, but these errors were encountered: