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

[Development of GNU's TLS library]

> The blocker in the past was the fact that `gnutls_record_send` and `gnutls_record_recv` would only do whatever they were asked (read and write). Currently however that's not the case, and `gnutls_record_recv` has internal logic which allows it to do more than just receiving data (e.g., already handles rekey).

I was wrong on the above. There was not such logic, and as such the introduction of such a simplification will bring that in.

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