[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_2764483021


@jas: I wasn't saying that GNUTLS should have returned all-clear.  I said it could have used a different error code that tells apart the "broken without any pending input" from "broken in the middle" kind of situation.  Right now, it's impossible to tell "how bad" the abrupt termination was.  Even though I understand (from reading the provided links to the standard and the discussion) that a bare EOF without "close-notify" is a serious protocol error, regardless.

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