The following command causes the SFTP session to bail out with the error WS_OVERFLOW_E:
sftp -o RekeyLimit=100 user@localhost
Assuming user is a real user on the sftp server, which is listening on localhost at the standard port.
My tests have shown that the issue doesn't manifest itself with the echoserver, however we've implemented a slightly different worker loop than the one being used by the echoserver, and that might be the trigger reason.
Our analysis identified the problem to be here:
Simply OR-ing ret == WS_WANT_READ on that line seems to fix the issue.
The following command causes the SFTP session to bail out with the error
WS_OVERFLOW_E:Assuming
useris a real user on the sftp server, which is listening onlocalhostat the standard port.My tests have shown that the issue doesn't manifest itself with the
echoserver, however we've implemented a slightly different worker loop than the one being used by the echoserver, and that might be the trigger reason.Our analysis identified the problem to be here:
wolfssh/src/internal.c
Line 7847 in 74cf1d4
Simply OR-ing
ret == WS_WANT_READon that line seems to fix the issue.