You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mbed TLS needs this to align with other implementations, such as OpenSSL. Also providing a write() method instead of requiring knowing all the early data to be known before then handshake is easier for applications. See the proposal for reasonings.
This issue is created here for visibility. It is referring to this issue in the tls13-prototype fork: hannestschofenig#234
Do we need an mbedtls_ssl_get_early_data_status() alongside mbedtls_ssl_write_early_data() like in the prototype ?
The text was updated successfully, but these errors were encountered:
ronald-cron-arm
changed the title
Define the API for writing early data in TLS 1.3
Define the API for writing early data on client side in TLS 1.3
Sep 22, 2022
Suggested enhancement
Please see this proposal:
https://docs.google.com/document/d/1h0Uf9ULJA0IgHR2dWhNynatjihQEN5IiFkvmkZD_ikc/edit?usp=sharing
Justification
Mbed TLS needs this to align with other implementations, such as OpenSSL. Also providing a
write()
method instead of requiring knowing all the early data to be known before then handshake is easier for applications. See the proposal for reasonings.This issue is created here for visibility. It is referring to this issue in the tls13-prototype fork: hannestschofenig#234
Do we need an
mbedtls_ssl_get_early_data_status()
alongsidembedtls_ssl_write_early_data()
like in the prototype ?The text was updated successfully, but these errors were encountered: