You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
In the ssh transport, there is a timeout and it is only reset when the connection is lost. In the code, it says that the timeout is reset once the authentication succeeds. But I think this is not the case.
In the current state, when a user is connected and opens an interactive shell. Even there is data flow between the client and the server, the connection is timeout.
The timeout in the protocol.py is never reached unless it is less than that set in the transport.
To Reproduce
Steps to reproduce the behavior:
Login as a user and open a shell
Type something until the timeout is reached.
Expected behavior
My suggestion is to reset the timeout of the transport in the protocol right after the connectionMade() in HoneyPotBaseProtocol.
If you agree to the idea, I will make a change.
The text was updated successfully, but these errors were encountered:
Describe the bug
In the ssh transport, there is a timeout and it is only reset when the connection is lost. In the code, it says that the timeout is reset once the authentication succeeds. But I think this is not the case.
In the current state, when a user is connected and opens an interactive shell. Even there is data flow between the client and the server, the connection is timeout.
The timeout in the
protocol.py
is never reached unless it is less than that set in the transport.To Reproduce
Steps to reproduce the behavior:
Expected behavior
My suggestion is to reset the timeout of the transport in the protocol right after the
connectionMade()
inHoneyPotBaseProtocol
.If you agree to the idea, I will make a change.
The text was updated successfully, but these errors were encountered: