Hi Nikos,

Thanks for your answer. So, if I understood everything well I need the following to avoid blocking:

when reading from socket, first check if gnutls_record_check_pending() != 0, and if 0, check for select()

when writing, just select()

Is that it ?

Thanks !

If I understand correctly, using select() will be completely impossible with future versions of GnuTLS ?

Is there an equivalent to gnutls_record_check_pending() to know whether writing to the socket would block ?

Thanks.

Is it correct that gnutls_record_check_pending() only returns non-0 when there is a complete TLS record buffered? ie, if gnutls_record_check_pending() returns non-0, is it guaranteed that an immediately following call to gnutls_record_recv() will not return GNUTLS_E_AGAIN?

Thank you. We could fix it in gnutls 2.12.x and restore the old default, but we'll just postpone the inevitable for the next release that abolishes that functionality.

Unfortunately not :( I just wanted to test what was the issue. gnutls 2.12.0 changed the semantics of gnutls_transport_set_lowat() and the default value is zero.

There are two solutions.
1. Quick fix. Programs that require another value must explicitly call:
gnutls_transport_set_lowat (session, 1);

after (gnutls_init()).

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.

regards,
Nikos

Hello,
 If you revert the patch in unpatch.txt, do the issues go away?


(file #23212)