SOCKS bugs
Posted: Mon Nov 04, 2024 8:48 am
Hello,
I've noticed a couple of bugs in the current implementation of SOCKS server, up to version 7.17beta4
1. Connection is always terminated after <Connection Idle Timeout>, that is the timeout is not reset/updated when the data is passing through the SOCKS.
For example, when transferring files over FTP using FileZilla I get this message every 2 minutes (default Connection Idle Timeout):
2. The SOCKS Connection list doesn't show source IP when the server is in version 4 mode:
I've noticed a couple of bugs in the current implementation of SOCKS server, up to version 7.17beta4
1. Connection is always terminated after <Connection Idle Timeout>, that is the timeout is not reset/updated when the data is passing through the SOCKS.
For example, when transferring files over FTP using FileZilla I get this message every 2 minutes (default Connection Idle Timeout):
If I change Connection Idle Timeout to 1 minute, connections terminate every 1 minute:Error: GnuTLS error -110 in gnutls_record_recv: The TLS connection was non-properly terminated.
Status: Server did not properly shut down TLS connection
Error: Could not read from socket: ECONNABORTED - Connection aborted
Error: Disconnected from server
Error: File transfer failed after transferring 38,535,168 bytes in 120 seconds
BTW it would be great if per-connection idle timer column was added to SOCKS Connections list.Error: GnuTLS error -110 in gnutls_record_recv: The TLS connection was non-properly terminated.
Status: Server did not properly shut down TLS connection
Error: Could not read from socket: ECONNABORTED - Connection aborted
Error: Disconnected from server
Error: File transfer failed after transferring 27,000,832 bytes in 60 seconds
2. The SOCKS Connection list doesn't show source IP when the server is in version 4 mode: