-
Notifications
You must be signed in to change notification settings - Fork 6.2k
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
DTLS Connection ID Support #44914
DTLS Connection ID Support #44914
Conversation
The following west manifest projects have been modified in this Pull Request:
Note: This message is automatically posted and updated by the Manifest GitHub Action. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would be good to get a word from mbed TLS fork maintainers, whether I'd be even allowed to cherry-pick certain mbed TLS functionalities from upstream.
651eee5
to
faa4152
Compare
faa4152
to
3d7d194
Compare
DTLS systems can accept the Server Name Indication extension without using X509 certificates. Allow this for either MBEDTLS_X509_CRT_PARSE_C or CONFIG_MBEDTLS_DTLS. Upstream PR: zephyrproject-rtos/zephyr#44914 Signed-off-by: Pete Skeggs <peter.skeggs@nordicsemi.no>
DTLS systems can accept the Server Name Indication extension without using X509 certificates. Allow this for either MBEDTLS_X509_CRT_PARSE_C or CONFIG_MBEDTLS_DTLS. Upstream PR: zephyrproject-rtos/zephyr#44914 Signed-off-by: Pete Skeggs <peter.skeggs@nordicsemi.no>
Add function to get the peer CID. Add case to ztls_getsockopt_ctx() to call it when optname is TLS_DTLS_PEER_CONNECTION_ID. zephyrproject-rtos/zephyr#44914 Signed-off-by: Pete Skeggs <peter.skeggs@nordicsemi.no>
This updates commits from #36738, and builds on them.