[gnutls-devel] GnuTLS | Improve 0-RTT handling in gnutls-serv/gnutls-cli (!1936)

[Read-only notification of GnuTLS library development activities]

Sahil Siddiq commented on a discussion on src/cli.c: https://gitlab.com/gnutls/gnutls/-/merge_requests/1936#note_2352304633

 >  			     GNUTLS_TLS1_3) ||
 >  			    ((gnutls_session_get_flags(hd->session) &
 >  			      GNUTLS_SFLAGS_SESSION_TICKET))) {
 > +				max_early_data_size =

Understood. My primary concern with this change is allowing the client to use gnutls_record_set_max_early_data_size(). If someone inadvertently uses this function when writing a client application, it might introduce a bug since it'll now be possible to hard code this value in the client. How about printing a warning if this is called by a client?

-- 
Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/1936#note_2352304633
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/20250217/571f76e2/attachment.html>