[gnutls-devel] GnuTLS | GnuTLS sends protocol_version alert when client message contains unrecognized version (#1230)

Read-only notification of GnuTLS library development activities gnutls-devel at lists.gnutls.org
Tue May 11 20:17:23 CEST 2021

Daiki Ueno commented on a discussion: https://gitlab.com/gnutls/gnutls/-/issues/1230#note_572952544

OK, thank you for the clarification. I misread `TlsPlainText.legacy_record_version` as `ClientHello.legacy_version`.

Still, I'm wondering whether we should implement the logic given in the description, i.e., special casing 0x03XX. Given RFC 8446 supersedes 5246 I am skeptical that we need to strictly follow that rule; what do you think?

Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/issues/1230#note_572952544
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/20210511/b3a4ffdb/attachment.html>

More information about the Gnutls-devel mailing list