-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TLS1.3 write early data #6542
TLS1.3 write early data #6542
Conversation
To match RFC, early data MUST be written after ClientHello ASAP. There is an issue for hybrid mode which described in #6486 (comment) . It should be dig and figure out best solution. |
d4f1306
to
99a7839
Compare
99a7839
to
56d5624
Compare
We are now converting older PRs to draft PRs where the following conditions are met: They have not been updated in the last 3 months, and they need more than non-trivial work to complete. |
e732ba2
to
4221aba
Compare
3741885
to
d36698d
Compare
For the time being, we should only allow early data in resumption and tls13 only mode for client side |
Signed-off-by: Xiaokang Qian <[email protected]>
Signed-off-by: Xiaokang Qian <[email protected]>
Signed-off-by: Xiaokang Qian <[email protected]>
Signed-off-by: Xiaokang Qian <[email protected]>
Signed-off-by: Xiaokang Qian <[email protected]>
b818179
to
e911b1a
Compare
Add API mbedtls_ssl_write_early_data()
Add API mbedtls_ssl_get_early_data_status()
Write early data at the first flight.
Add machine stat: MBEDTLS_SSL_EARLY_APP_DATA