[gnutls-devel] GnuTLS | transparent client re-authentication (#571)

Development of GNU's TLS library gnutls-devel at lists.gnutls.org
Thu Oct 4 13:07:10 CEST 2018

I don't think that is a problem as long as you update the docs to say that `gnutls_record_recv` *might* also send data if needed.

Since this will not be default behavior (will only happen when certain flags are provided) it won't break existing code, and those who use these flags know what they're up to.

For instance, if I'm working with non-blocking sockets and calling `gnutls_record_recv` I know I need to check the socket's ready for both reading & writing. If my application is compiled against an older version of GnuTLS that doesn't support this, the code would still work.

Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/issues/571#note_106440627
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/20181004/7daf49ef/attachment.html>

More information about the Gnutls-devel mailing list