I observe the bug too (after 163.840 bytes) but even with GnuTLS 2.12.20 installed from Debian
ord GnuTLS 3.0.11.
checked out a svn version but that still doesnt resolve the problem (it shows 2.12.20 as version there too)
seems to be the code still has to be fixed to work with 2.12 or 3.0 versions
i didnt find "fixed" code like stated in https://savannah.gnu.org/support/?107660
in a search in filezilla cpp files
ord GnuTLS 3.0.11.
checked out a svn version but that still doesnt resolve the problem (it shows 2.12.20 as version there too)
seems to be the code still has to be fixed to work with 2.12 or 3.0 versions
i didnt find "fixed" code like stated in https://savannah.gnu.org/support/?107660
in a search in filezilla cpp files
Quote:
1. Quick fix. Programs that require another value must explicitly call:
gnutls_transport_set_lowat (session, 1)
2. Long-term fix. Because later versions of gnutls abolish the functionality of using the system call select() to check for gnutls pending data, the function
gnutls_record_check_pending()
has to be used to achieve the same functionality.
gnutls_transport_set_lowat (session, 1)
2. Long-term fix. Because later versions of gnutls abolish the functionality of using the system call select() to check for gnutls pending data, the function
gnutls_record_check_pending()
has to be used to achieve the same functionality.