[gnutls-devel] GnuTLS | GNUTLS error at the end of connection (#1739)

[Read-only notification of GnuTLS library development activities]

alavrentiev commented: https://gitlab.com/gnutls/gnutls/-/issues/1739#note_2764353034


Thank you for your reply!

> and nothing in your report suggests gnutls misbehaving.

The other TLS implementations (curl, lwp-request and mbedTLS included) process the request without throwing any errors.  GNUTLS behavior is drastically different (and fussy).

Even though there was no "close_notify" received, there was no outstanding unprocessed input at the time of the EOF, either.  So instead of the generic "closed too early" error, GNUTLS could have used some special error code that could help distinguish this corner case condition.

-- 
Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/issues/1739#note_2764353034
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/20250919/7a6ee109/attachment.html>