jerryt92 opened a new issue, #860:
URL: https://github.com/apache/mina-sshd/issues/860

   ### Version
   
   2.16.0
   
   ### Bug description
   
   Steps to Reproduce
   
   1. Start an SshServer instance using the default configuration (where 
REKEY_BYTES_LIMIT is 1073741824 bytes / 1GB).
   
   2. Establish an SSH connection with dynamic port forwarding (e.g., ssh -D 
1080 user@host).
   
   3. Configure an FTP client (e.g., FileZilla) to use the SOCKS5 proxy 
(localhost:1080).
   
   4. Connect to an FTP server through the proxy and start transferring large 
files (totaling > 1GB).
   
   5. Result: The FTP transfer speed drops to zero and the connection hangs 
exactly around the 1GB mark. The SSH tunnel effectively stops forwarding data.
   
   Environment
   SSHD Version: 2.16.0
   
   Java Version: [e.g., OpenJDK 21.0.7.0.7]
   
   OS: [Windows 11]
   
   Client: [SSH-2.0-SurgeSSHClient_1.0]
   
   ### Actual behavior
   
   I am experiencing an issue where file transfers hang/freeze when using 
dynamic port forwarding (or heavy traffic tunneling) once the data transfer 
volume reaches approximately 1GB.
   
   After investigating, I confirmed that this issue is directly related to the 
Key Re-exchange (Rekeying) mechanism. The hang occurs exactly when the default 
REKEY_BYTES_LIMIT (which defaults to 1GB) is reached.
   
   ### Expected behavior
   
   The Key Re-exchange process should handle high-throughput traffic gracefully 
without blocking the I/O session, allowing the transfer to continue after the 
handshake.
   
   ### Relevant log output
   
   ```Shell
   
   ```
   
   ### Other information
   
   _No response_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to