[gnutls-devel] GnuTLS | Early data issues in QUIC use (#1216)

Read-only notification of GnuTLS library development activities gnutls-devel at lists.gnutls.org
Thu Apr 29 08:04:02 CEST 2021

Daiki Ueno commented:

For (4) we should probably add a couple of functions dedicated for those: `gnutls_early_cipher_get` and `gnutls_early_prf_hash_get` for example.

(2) was a oversight; I didn't realize there will be a use-case of getting early write key on the client side.

For the others, I'm thinking to reuse the `GNUTLS_ENABLE_EARLY_DATA` flag for client, with a new flag to suppress EndOfEarlyData:
gnutls_init(&session, GNUTLS_CLIENT |
                      GNUTLS_ENABLE_EARLY_DATA |
then even if `gnutls_record_send_early_data` is not called, early data will be indicated.

Would that suffice the use with QUIC?

Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/issues/1216#note_563304680
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/20210429/379ac1d7/attachment.html>

More information about the Gnutls-devel mailing list