[gnutls-devel] GnuTLS | Improve 0-RTT handling in gnutls-serv/gnutls-cli (!1936)
Read-only notification of GnuTLS library development activities
gnutls-devel at lists.gnutls.org
Sun Feb 16 23:50:51 CET 2025
Daiki Ueno commented on a discussion on src/cli.c: https://gitlab.com/gnutls/gnutls/-/merge_requests/1936#note_2350146964
> GNUTLS_TLS1_3) ||
> ((gnutls_session_get_flags(hd->session) &
> GNUTLS_SFLAGS_SESSION_TICKET))) {
> + max_early_data_size =
The problem is that the data (session ticket) retrieved with `gnutls_session_get_data2` can only be decrypted by the server and from anyone else (including the client), it looks like an opaque blob.
We could store max_early_data_size as a metadata along with the session ticket to eliminate the need of calling get/set_max_early_data, though I guess it would be a non-trivial change.
--
Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/1936#note_2350146964
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/20250216/f1f22a07/attachment.html>
More information about the Gnutls-devel
mailing list