[gnutls-devel] GnuTLS | The GNUTLS Release 3.3.16 has a bug in the DTLS Non-Blocking logic, bug located at gnutls-3.6.16/lib/record.c in function _gnutls_recv_in_buffers at lines 1307 and 1322 (#1413)

[Read-only notification of GnuTLS library development activities]

Daiki Ueno commented:


Looks like this is the first commit that changed the behavior:
https://gitlab.com/gnutls/gnutls/-/commit/2a46a94fab312f584db071bc23668c942f8e439e#262a8c0db6e7caeff5570034957c36922727d5b7_1157_1156

This aligns with the documentation of `gnutls_transport_set_pull_timeout_function`, which says: "The callback will not be used when the session is **in TLS mode** with non-blocking sockets."

Perhaps we should conditionalize it based on which TLS or DTLS is used?

-- 
Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/issues/1413#note_1133976820
You're receiving this email because of your account on gitlab.com.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnutls-devel/attachments/20221013/196cb6d0/attachment.html>