[gnutls-devel] GnuTLS | Client side: unable to detect early data size of UINT32_MAX (#1619)

[Read-only notification of GnuTLS library development activities]

Stefan Eissing created an issue: https://gitlab.com/gnutls/gnutls/-/issues/1619



Working on curl's QUIC support using gnutls + ngtcp2, I seem to be unable to distinguish
between a server wihout Early Data support and the many implementations (Caddy, nghttpx) 
that announce a max early data of UINT32_MAX.

`session->security_parameters.max_early_data_size` is initialized on the client side as
UINT32_MAX and, if the server does not send the extension in the tickets, it is not set 
to 0.

I fail to find an alternative way of detecting that the server does not support it. Given
that, would it not be correct to set the value to 0 when receiving a session ticket that
does not carry the extension?

Many thanks for the help.

-- 
Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/issues/1619
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/20241129/269d02d0/attachment.html>