[gnutls-devel] GnuTLS | Draft: Set default value of early date size for client to 0 (!1906)
Read-only notification of GnuTLS library development activities
gnutls-devel at lists.gnutls.org
Wed Dec 18 19:04:15 CET 2024
Merge request https://gitlab.com/gnutls/gnutls/-/merge_requests/1906 was reviewed by Sahil Siddiq
--
Sahil Siddiq commented on a discussion: https://gitlab.com/gnutls/gnutls/-/merge_requests/1906#note_2265909200
Hi, I think I misunderstood how "early data" is negotiated. I spent some time understanding the implementation of early data, session tickets and tests/tls13-early-data-neg*.c. My understanding is that "early data" is negotiated when the server sends a session ticket with the relevant extension rather than simply being initialized with `GNUTLS_ENABLE_EARLY_DATA`.
I have modified tests/tls13-early-data-neg2.c instead of creating a new test. The test currently makes use of 2 sessions to check that "early data" is rejected by the server when resumption fails (in the current case because the first session ticket key is overwritten).
This test now establishes 3 sessions instead of 2. No session ticket is sent during the first session to negotiate "early data". Due to this, "max_early_data_size" for the client is 0 after resumption is attempted in the second session.
The second and third sessions together perform the checks done in the original test.
--
Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/1906
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/20241218/e50153b2/attachment-0001.html>
More information about the Gnutls-devel
mailing list